On Fri, 27 Sep 2002, Tabor J. Wells wrote:
> That's the more interesting question I think. Why is your server sending
> EHLO/HELO twice?
There was once a bug that did this under some circumstances. It was
fixed in release 4.03. Here's the ChangeLog entry. Does it fit your
case?
11. When Exim received a message other than from the daemon, there were two
situations in which it did not re-exec itself for delivery: when it was
running as root, or when it was running in an unprivileged mode. This was
an attempt to save some resources (very early Exims ran as root more often)
but has turned out to be pretty rare. A bug has been discovered in this
case: if the incoming message was on a TLS session (from inetd, for
example), but the outgoing delivery was on an unencrypted SMTP connection,
Exim got confused. The effect was minimal: it sent two EHLO commands, but
otherwise worked. Multiple EHLOs are not an error, according to the RFCs,
but there was at least one broken MTA that objected. This error would have
occurred only when synchronous delivery (-odi or -odf) was specified.
While sorting this out, I have abandoned the logic that did a delivery
without forking in the interests of simplicity. This was an even rarer
case: it only happened when Exim was running as root or in an unprivileged
mode AND synchronous delivery was specified.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
