Gnus development mailing list
 help / color / mirror / Atom feed
From: Richard Riley <rileyrg@googlemail.com>
To: ding@gnus.org
Subject: Re: making sendmail call to msmtp asynchronous?
Date: Wed, 30 Mar 2011 14:01:35 +0200	[thread overview]
Message-ID: <507hbgq0kg.fsf@news.eternal-september.org> (raw)
In-Reply-To: <20110330093608.GA22794@apollo.emma.line.org> (Matthias Andree's message of "Wed, 30 Mar 2011 11:36:08 +0200")

Matthias Andree <ma+gnus@dt.e-technik.uni-dortmund.de> writes:

> On Wed, Mar 30, 2011 at 08:38:46AM +0200, Richard Riley wrote:
>> Not without pain. Of course. Exim4 is up there with the worst when it
>> comes to "simple tweaks" and enabling exim4 for multiple smarthosts
>> proved impossible (for me) give or take despite some old configs out
>> there in google land for exim1-3 but not 4. Why not use exim4s smtp send
>> facility? Its a pain if you travel : here I sit on holiday and smtp
>> ports for outgoing are blocked by the ISP and/or the hotel router. Gah!
>
> While I could offer you sample configs from my Cygwin installation, I've
> found out the hard way (this time on FreeBSD) that Exim4 has a very
> awkward lock-destination-sites behaviour that requires major manual
> interventions to purge the retry/site database to get mails unstuck,
> thus I decided I'm not going to install any more of that.
>
> While Postfix is a bit more of an effort to configure (enable
> sender-based authentication, enable sender-based relay, enable smtp (not
> smtpd)-side tls, enable smtp-side sasl, permit plaintext authentication
> on secure tls channels, set up all the maps, I find it's more
> transparent and has less magic special casing underneath that confuses
> the heck out of myself.
>

Much as I dislike Exim4 docs, I have to stick up for it here. Using a
single smarthost as I described is pretty straightforward.

Clearing frozen mails caused by a destination refusing your mail because
your IP is blacklisted or smtp ports are blocked is a google away.

I did originally use the exim4 sendmail interpretation (having first had
my business/home IP cleared out of spamhaus! It took about a day for all
major email providers to get the updated spam lists and see my ip
cleared) and that was great but of course my recent roaming adventures
put paid to that and its back to gmail smtp smart hosts.

-- 

☘ http://www.shamrockirishbar.com, http://splash-of-open-sauce.blogspot.com/ http://www.richardriley.net



  reply	other threads:[~2011-03-30 12:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21  6:19 Eric Abrahamsen
2011-03-21  6:55 ` Erik Colson
2011-03-21  7:24   ` Eric Abrahamsen
2011-03-29 18:26 ` Lars Magne Ingebrigtsen
2011-03-30  0:51   ` Eric Abrahamsen
2011-03-30  6:38     ` Richard Riley
2011-03-30  9:36       ` Matthias Andree
2011-03-30 12:01         ` Richard Riley [this message]
2011-03-30 13:40           ` using Exim 4 w/ multiple smarthosts (was: making sendmail call to msmtp asynchronous?) Matthias Andree
2011-03-30 13:30             ` using Exim 4 w/ multiple smarthosts Richard Riley
2011-03-30 19:22         ` making sendmail call to msmtp asynchronous? Leonidas Tsampros
2011-03-31 19:34           ` Sivaram Neelakantan

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=507hbgq0kg.fsf@news.eternal-september.org \
    --to=rileyrg@googlemail.com \
    --cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).