------- You are receiving this mail because: -------
You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=736
Phil Pennock <exim-dev@???> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |exim-dev@???
--- Comment #7 from Phil Pennock <exim-dev@???> 2008-07-17 00:40:56 ---
You have serialize_hosts set on the transport to match everything, so there can
only be one connection at a time to a given host, controlled by hints.
Is there another exim process running (exiwhat should tell you this)?
Did the system reboot and did you set up the DB hints nuking recommended in the
documentation of serialize_hosts ?
"exim_dumpdb /var/spool/exim misc" might be informative.
Note that serialize_hosts is a rather rare option to see (in my experience)
since most people seem happy to have a few concurrent connections per host so
that if one stalls (eg, antivirus on the remote side gets unhappy at a message)
it doesn't stop the entire flow. You have an option here explicitly designed
to prevent delivery to the remote host.
I'm also curious about hint lifetime and if you had any stale hints from before
you added "self = send" to the configuration to permit the host to send to
itself, as the primary MX.
It would be useful to see a debugging run for the actual delivery of a mail,
"exim -d -odf -t" and supply a mail on stdin; that should show the debugging
for the use of the transport and would let you/us see why the preferred MX is
skipped. Perhaps -d+transport+hints_lookup+host_lookup to get more data if the
initial test doesn't provide enough information.
--
Configure bugmail:
http://bugs.exim.org/userprefs.cgi?tab=email
