From: Philippe LeCavalier <support@plecavalier.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] background or queue msg sending
Date: Thu, 17 Mar 2011 21:31:21 -0400 [thread overview]
Message-ID: <1300411874-sup-4334@plc.intranet.plecavalier.com> (raw)
In-Reply-To: <1300408936-sup-5939@tilus.net>
Excerpts from Tero Tilus's message of Thu Mar 17 20:53:46 -0400 2011:
> Philippe LeCavalier, 2011-03-17 22:10:
> > > You need to wait? I don't. Sup is instatly back after hitting 'y'.
> > That's because of your connection speed.
>
> Are you kidding?
No I wasn't.
>I've sent mail using sup when hanging on GPRS (roughly 30 kbps and
>1500ms ping lag) in a train moving 200 km/h. Instant send. If it was
>about uplink speed I definitely would have experienced it then.
I agree. I understand now that it was, as explained, msmtp waiting for
the remote smtp session to finish. Whcih, whether I knew that or not
wasn't really my point. I just wanted to throw the process of msmtp
blocking while talking to the relay in the background. But I see know
that using the local MTA would be just as 'instant' as putting the
buffer in the background. Or perhaps should I say making that need
obsolete...
--
Thanks,
Phil
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-03-18 2:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 14:17 Philippe LeCavalier
2011-03-17 15:32 ` Bruno d'Arcangeli
2011-03-17 19:15 ` Philippe LeCavalier
2011-03-17 19:55 ` Ben Walton
2011-03-17 20:16 ` Kevin Riggle
2011-03-17 23:10 ` Philippe LeCavalier
2011-03-17 19:54 ` Tero Tilus
2011-03-17 20:10 ` Philippe LeCavalier
2011-03-17 22:32 ` Sascha Silbe
2011-03-17 23:08 ` Philippe LeCavalier
2011-03-18 1:34 ` Philippe LeCavalier
2011-03-18 0:53 ` Tero Tilus
2011-03-18 1:31 ` Philippe LeCavalier [this message]
2011-03-17 22:42 ` Sean Escriva
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1300411874-sup-4334@plc.intranet.plecavalier.com \
--to=support@plecavalier.com \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox