[Mailman-Users] Mailman reusing message-id, leads to duplicate message suppression
barry at list.org
Wed Nov 6 17:03:15 CET 2013
On Nov 06, 2013, at 09:51 AM, Ralf Hildebrandt wrote:
>> 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.
This probably makes sense, so please submit a bug.
>>  It's surprisingly difficult to handle duplicates truly gracefully.
I've found 'd' in my MUA works about as well as anything. :)
>> For example, I personally consider the mailing list copy to be the
>> "canonical" copy of a post, but direct CCs often arrive more quickly.
>Same here. Happens all the time.
Indeed. It would be great if you could suppress the direct CC, but of course,
that's impossible since Mailman never sees them. The best you can do is
suppress the list copy, but that isn't a great solution either if your MUA
knows how to do sane things based on the List-* headers.
More information about the Mailman-Users