----- Forwarded message from Jason Gunthorpe <jgg@???> -----
Delivered-To: joey-packages-exim@???
Date: Sun, 15 Nov 1998 14:46:46 -0700 (MST)
From: Jason Gunthorpe <jgg@???>
To: exim@???
Subject: Bizzar MX behavoir
I can't seem to find the upstream bug reporting address in the doc..
bother.
Exim has been giving me pain these days because of it's screwy MX mode. If
it accepts a message for MXing (because it is in the mx list for a host)
and then goes to relay it and doesn't find an interface that matches
something in the mx list it will attempt to send it to the other MX's!
IMHO exim should not attempt other mx's if the message matches a host in
relay_domains. Currently it looks at the MX list and tries to decide if it
is in it.
What happened to me is one of my multi-homed mailhosts lost one interface
so exim did not know that it was in the mx list of a host and started
sending mail to the only avail mx which sent it back to exim and so on
creating a mail loop and bouncing all the mail. The solution seems to be
to set the 'local_interfaces' directive to all your interfaces so exim can
find itself in the mx lists, but this seems kludgy and unintuitive somehow
:<
Thanks,
Jason
----- End forwarded message -----
--
*** Exim information can be found at
http://www.exim.org/ ***
