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

Top Page
Delete this message
Reply to this message
Author: Mike Brudenell
Date:  
To: Exim Users
Subject: Re: [exim] Exim not always logging Message-ID
On 13 June 2016 at 21:40, Jeremy Harris <jgh@???> wrote:

> I'd prefer if the logging of this was optional - say, another
> log_selector flag.
>


That sounds a good move, and hopefully would be acceptable to those who
want to always see the Message-Id (whether received or generated) as well
as those who aren't that interested in the value of a generated id but
instead just knowing whether an incoming message had one or not.


> Also, should it tagged in some different way,
> to differentiate it from an id received with the message
> (which could have been generated by some other Exim instance)?
>


On 13 June 2016 at 21:50, Heiko Schlittermann <hs@???> wrote:

>
> … id=<generated id>     # logged as always, because it *is* a message id
>   fixed=id,sender,date  # logged if +fixes is active
> or
>   id*=<generated id>    # marks the id as a fixed one



The idea of introducing a "fixed=" item, presumably showing only those
items that were actually fixed up by this Exim, is interesting. This could
then not only highlight clients that don't generate Message-ID headers, but
also ones that don't supply a Date header, etc. Might be useful in
detecting issues with client software that could be fixed/improved?

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