On 11/5/13, 6:59 PM, Stephen J. Turnbull wrote: > Note that the subject is incorrect. Mailman is not reusing the > Message-ID, it is refusing to alter it which is correct behavior > according to RFC 5322 (Message-ID is an originator field). > > I believe that according to RFC 5322 (and predecessors) Mailman SHOULD > add a Resent-Message-ID to indicate that it handled the message, but I > doubt this would change the duplicate-suppression behavior of Gmail > and MS Exchange. > It is not clear to me that mailman should add the Resent-* headers. The RFC states:
"Resent fields SHOULD be added to any message that is reintroduced by a user into the transport system." and later "They MUST NOT be used in the normal processing of replies or other such automatic actions on messages." Mailman isn't really a "user", and is "automatic" so I think the second clause is more applicable. -- Richard Damon ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
