Re: master mail problems -- help needed
On Sat, Nov 26, 2005 at 02:00:48PM +0100, Florian Weimer wrote:
> >From time to time, master seems to bounce mail routed to mail.enyo.de
> with the following error message:
> retry time not reached for any host after a long failure period
> Is anybody experiencing a similar problem?
> I tried to debug it myself, using the information I could access on
> master, but I couldn't gather enough evidence to present to the
> postmasters so far.
But other DD's can also only do a limited amount of research, the only
way to really find out is asking a postmaster -- this isn't a
prosecution, so 'evidence' is not needed, I'd say (though, a copy of one
bounce message with full headers would be the minimum I'd expect,
because otherwise debugging is close to impossible).
In general, this failure means that for 4 consecutive days the
a connection attempt that happens roughly every 8 hours fails
(connection refused, a timeout, HELO refused, stuff like that). Are you
sure that this condition can never have happened? I see you only have
one MX, for increased reliability and for cases when for example there's
a routing problem somewhere between master and that one single MX, add a
When an exim mailserver is really bogged down under mail load, attempts
can be made even less often.
> IIRC, when there are no prolonged connectivity
> problems, the error message is characteristic of a broken Exim retry
> configuration (no retry section at all, or something like that), but
> master's configuration seems to be fine in this regard.
> The host mail.enyo.de had some intermittent connectivity problems
> during the past few weeks (downtimes of about one hour every couple of
> days, nothing which should cause Exim to run past its configured retry
> limit). But this has been fixed, and the sporadic bounces continued.
> The other problem is a certain sluggishness when one of those botnets
> attempts to send spam to hundreds of message IDs, but these attacks
> last a couple of minutes only, and master should be able to cope with
I'd really look into a secondary MX, but if it's indeed only there two
problems at the frequency you say, it shouldn't really be possible that
this is the cause.
> This problem has gained some unexpected urgency because I was kicked
> off the PTS due to these bounces (I think so, I haven't been shown one
> of the PTS bounces). On the other hand, it rules out my .procmailrc
> on master as an error source (because PTS mail gets sent to
> <firstname.lastname@example.org> directly).
There is no automatic bounce handling for the PTS, that's still on the
Jeroen van Wolffelaar
Jeroen@wolffelaar.nl (also for Jabber & MSN; ICQ: 33944357)