Re: [exim] Exim not always logging Message-ID

Top Page
Delete this message
Reply to this message
Author: Jeremy Harris
Date:  
To: exim-users
Subject: Re: [exim] Exim not always logging Message-ID
On 01/06/16 12:16, Mike Brudenell wrote:
> However if the message arriving over SMTP *does not include* a
> "Message-ID:" header then no value gets logged.


Not looked at the source yet, but that's kinda-reasonable: what
was there at accept time is logged.


> Is this a bug/oversight?


Both?

> Is it a feature I could request, or are there technical reasons why it
> couldn't be logged?


I doubt you've missed anything, and it is a reasonable request
( https://bugs.exim.org/ please ). Would you prefer a separate
log line? Message-ID on delivery lines? An Event raised?


> This is making it a real pain to try and trace a message generated by an
> on-site system, sent out through Exim on our local gateways to an external
> host, which (I think, but am trying to prove) is relaying it back to our
> Google-hosted mailboxes. The message-id would be the information to link
> the outgoing entry in Exim's logs to the incoming messages in Google's logs
> whilst having no access to the logs of the intermediate server.


Aha. I was going to suggest the confirmation (C=) field, but you
just torpedoed that...

Sounds like you would like a quick patch to test :)
Can you compile from source?
--
Cheers,
Jeremy