Tony Earnshaw --> dkim-milter-discuss (2008-01-21 12:53:35 +0100):
> Correct me if I'm wrong anybody, but a Message-ID is supposed to be 
> unique. See rfc2822 3.6.4. Identification fields:
> 
>     The "Message-ID:" field contains a single unique message identifier.
>     The "References:" and "In-Reply-To:" field each contain one or more
>     unique message identifiers, optionally separated by CFWS.

That's correct, and two paragraphs later there's the following note:

   Note: There are many instances when messages are "changed", but those
   changes do not constitute a new instantiation of that message, and
   therefore the message would not get a new message identifier.  For
   example, when messages are introduced into the transport system, they
   are often prepended with additional header fields such as trace
   fields (described in section 3.6.7) and resent fields (described in
   section 3.6.6).  The addition of such header fields does not change
   the identity of the message and therefore the original "Message-ID:"
   field is retained.  In all cases, it is the meaning that the sender
   of the message wishes to convey (i.e., whether this is the same
   message or a different message) that determines whether or not the
   "Message-ID:" field changes, not any particular syntactic difference
   that appears (or does not appear) in the message.

And that's BTW exactly what e.g. mutt does when you bounce / resend a
message: it retains the Message-ID and creates a new Resent-Message-ID.


> If a client MUA or an MTA sends a message twice, both will have discrete 
> Message-IDs. Alternatively, either the client software is badly broken 

No. It's broken if it does change the Message-ID (see above).


Regards, Jukka

-- 
bashian roulette:
$ ((RANDOM%6)) || rm -rf ~

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
dkim-milter-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss

Reply via email to