[Mailman-Developers] Mailman introducing spurious References: or In-Reply-To: headers?

[Mark Sapiro]

On 10/27/2014 06:59 AM, Daniel Kahn Gillmor wrote:
> 
> over on dns-privacy at ietf.org, one of the participants (Hosnieh Rafiee,
> cc'ed here) suggests that mailman appears to be introducing spurious
> References: and In-Reply-To: headers (see the attached message below for
> some of the discussion.
> 
> Can you confirm whether this is a function of mailman (e.g. to try to
> merge threads between people whose MUAs don't properly set In-Reply-To:
> or References:?  If so, is there anything we can do to avoid it
> happening in the future?


Mailman does not do this. Mailman, at least standard GNU Mailman, does
not alter References: or In-Reply-To: headers in any way.

Mailman's pipermail archiver makes use of these headers in determining
threading in its archives, but it neither adds nor removes them or
anything from them and anything it does has no effect on delivered
messages in any case.

The only thing in Mailman which manipulates these headers is the DMARC
mitigation wrap message option introduced in Mailman 2.1.16 which merely
copies these if they exist from the wrapped message to the outer
wrapping message.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20141027/be75e5ec/attachment.sig>