OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: Message ID duplication

From: Matthew Sullivan (matthewsorbs.net)
Date: Mon May 02 2005 - 19:19:40 CDT


Wietse Venema wrote:

>Peter:
>
>
>>I think I found a 'new' bug in postfix (it actually applies to all
>>MTAs). postfix accepts a Message-Id supplied by the MUA or upstream
>>origin.
>>
>>
>
>Please cite the RFC paragraph that is being violated.
>
>
>
Wietse, I suspect you've asked for that because like me you don't think
there is one.

>>If that Message-Id is duplicated then downstream MUAs and email
>>list managers will break, and start deleting threads resp. locking up on
>>attempts to thread. This applies to any message that has headers like:
>>
>>Message-Id: <a.dulicate.id>
>>References: <a.duplicate.id>, ...
>>
>>this breaks at least Thunderbird and prevents threading by mailing list
>>archivers. The message id could be checked by postfix and changed to
>>something different if it appears in References.
>>
>>
Peter:

Now this I do know is an RFC violation (don't ask what RFC I can't
remember - likely 2822)... Messages IDs generated should be unique.
Now as I see it unless Postfix is generating the duplicate Message IDs
Postfix is not violating anything - the upstream that is generating the
duplicate Message ID, whether MTA or MUA is technically violating the RFC.

I'll look up the reference if needed, I wouldn't be surprised if the RFC
says that it should *try* to generate unique message ids.

Regards,

Mat