Jeremy Harris wrote:
[...]
> It certainly never *accepted* the second mail, hence the lack of
> a "<=" line for it.
Yes, certainly. But in my experience Exim has always put something in
the logfile if anything had happened. Something should be there.
>
> Ideas:
>
> - add smtp_protocol_error and smtp_syntax_error to your log_selector
> - can you get a packet-level trace of such a conversation? Tcpdump
> lets you filter by IP.
I'll give it a try as soon as I a) have my personal exchange-admin
available again (i.e. tomorrow) and b) the issue shows up again (the
messages timed out and have been sent back).
> - is pipelineing offered by exim? Try turning it off
> (pipelining_advertise_hosts)
It should be enabled. But I doubt that pipelining has happened,
according to the exchange-logfiles. We'll know more when I manage to
tcpdump a session.
> - can you run a conversation like this into exim in debug-mode,
> and capture the console output?
Its tricky since the server definitly is quite busy. I could try to
create a spare-server, though.
--
CU,
Patrick.
