On 1 June 2016 at 13:18, Jeremy Harris <[email protected]> wrote: > It matches the documentation, which states: > > "id message id for incoming message" > > (Section 13, Chapter 52) >
In one sense yes. In another one could argue that, under appropriate circumstances, Exim "fixes up" a faulty incoming message that lacks a Message-ID header by generating one. Does such a generated message-id form part of the "incoming message" (and hence should be logged on the "<=" line)? An interesting question: it's added within the receive_msg() function that builds the incoming message to return to the main body of Exim so one could reasonably say Yes. The fact it was added by Exim in response to the admin deliberately setting submission mode is arguably not relevant. Regardless of that debatable detail, it should be recorded *somewhere* in the logfiles. Without this it's impossible to find out the message-id of the message transmitted onward to make tracing possible/easier/more certain. Cheers, Mike B-) -- Systems Administrator & Change Manager IT Services, University of York, Heslington, York YO10 5DD, UK Tel: +44-(0)1904-323811 Web: www.york.ac.uk/it-services Disclaimer: www.york.ac.uk/docs/disclaimer/email.htm -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
