From: Kevin Riggle <kevinr@free-dissociation.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] background or queue msg sending
Date: Thu, 17 Mar 2011 16:16:09 -0400 [thread overview]
Message-ID: <1300392204-sup-5911@black-opal.free-dissociation.com> (raw)
In-Reply-To: <1300385916-sup-3971@plc.intranet.plecavalier.com>
Excerpts from Philippe LeCavalier's message of Thu Mar 17 15:15:30 -0400 2011:
> Even if Exim or Postfix might act faster than msmtp(what I'm using now)
> sup is set up in a way that it waits for the process to terminate before
> bringing me to the previous buffer. What I'd like to suggest is that sup
> should immediately bring you to the previous buffer.
Exim or Postfix will both act as the local message queue for you, unlike
msmtp which blocks while it talks to the upstream remote mail server.
It's not so much Sup's blocking as msmtp's blocking here which is the
problem, IME -- talking to the local MTA is wicked fast, and you can set
your local MTA to use your upstream remote mail server as its smarthost
-- and there's no reason to add a message queue to Sup if your MTA can
handle it.
Given Exim's recent security troubles I'd recommend Postfix.
- Kevin
--
Kevin Riggle (kevinr@free-dissociation.com)
http://free-dissociation.com
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-03-17 21:56 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 [this message]
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
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=1300392204-sup-5911@black-opal.free-dissociation.com \
--to=kevinr@free-dissociation.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