On Thursday 11 April 2013, Stephen J. Turnbull wrote:
> No, by definition it's a nasty feature, as it involves nonconformance
> to RFC 5322.
How so? I see two places in section 3.6.4. that suggest otherwise.
" A message
identifier pertains to exactly one version of a particular message;
subsequent revisions to the message each receive new message
identifiers."
So if a list adds a footer to the body of a message (many do) then that
implies that the Message-ID /should/ be changed. Obviously Mailman does not
want to break threading for no good reason. However fighting Gmail's
annoying feature with a less annoying kludge is a good enough reason in my
book.
Just below, same section 3.6.4., top of page 25, "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."
If the sender ticks the box telling Mailman to change the Message-ID then
they get to take the heat. Other settings have brief descriptions / warnings
so a sentence warning about breaking threading and the other issues you
raise would not be out of place.
--
William
------------------------------------------------------
Mailman-Users mailing list [email protected]
http://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:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
