Re: [Exim] $message_id is blank

Top Page
Delete this message
Reply to this message
Author: Philip Hazel
Date:  
To: Wakko Warner
CC: Kevin P. Fleming, exim-users
Subject: Re: [Exim] $message_id is blank
On Fri, 13 Jun 2003, Wakko Warner wrote:

> Interpretation... Tell me, what would be the difference between generating
> a message id at the start of the session (resetting on each reset) instead
> of after headers are received?


Wasted effort for the cases when the message is refused. I probably
originally did it the way it is as a copy from smail, which used the
inode number of the spool file in the id - the spool file isn't created
until the headers are read. Also, I guess I felt it wasn't necessary to
create it until it was needed.

The code also uses the existence of a message id to indicate "message
was received", so changing this would involve checking all those uses.
There would also have to be some hacking to make the microsecond
timestamp available in two different modules - at present it is all
handled in one place.

> What I woundup doing is generating a temp ID (something like
> TMP-${hmac{md5}{}{$pid-$tod_log}} and setting acl_m1 to it) then after data,


$pid-$tod_log isn't unique enough these days - that's why the message id
format changed in the latest releases of Exim.

--
Philip Hazel            University of Cambridge Computing Service,
ph10@???      Cambridge, England. Phone: +44 1223 334714.
Get the Exim 4 book:    http://www.uit.co.uk/exim-book