Exim logs the Message-ID: header of an incoming message in the "reception"
line. If there isn't a Message-ID: header, Exim adds one but doesn't log
it. [Per the Exim 4 book.]
So far, so good.
However, Eudora (5 and the newish 6) produces not a Message-ID: header but a
Message-Id: (little d) header. For example:
Message-Id: <p06002042bb8d133535a6@???>
Exim 4.10 appears to not put in a Message-ID: of its own, because the
Message-Id: is there, but not to log the id, because Message-ID: isn't
there.
Here's the reception of that message being logged:
2003-09-16 12:21:28 19zLOB-0000lm-00 <= tcijb@???
H=c66-235-28-31.sea2.cablespeed.com ([192.168.1.50]) [66.235.28.31] P=esmtp
X=TLSv1:RC4-SHA:128 S=495
In contrast, Entourage X produced for a test message:
Message-ID: <BB8CBC55.5333%jwblist@???>
and that got logged as
2003-09-16 13:10:47 19zM9v-0008Pu-00 <= jwblist@???
H=c66-235-28-31.sea2.cablespeed.com ([192.168.1.50]) [66.235.28.31] P=esmtp
S=541 id=BB8CBC55.5333%jwblist@???
We'll be moving to Exim 4.23 soon (not this week: we're upgrading our
scanning/sorting/processing system this week--one change at a time).
--John
