OT - EMEW (Enhanced Message-ID as Email Watermark) breaks pipermail threading

[Hugo van der Kooij]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jay R. Ashworth wrote:
> On Sun, Aug 24, 2008 at 09:35:19PM -0700, Mark Sapiro wrote:
>> I notice a few frequent posters on this list, including Jules since
>> late May, appear to receive list posts with Message-IDs munged with
>> EMEW watermarks. Thus their replies to list posts have In-Reply-To:
>> with the munged Message-ID which breaks threading in the pipermail
>> archive at <http://lists.mailscanner.info/pipermail/mailscanner/>
>> (every time Jules replies to a post, a new thread is started).
>>
>> I am a Mailman developer and am concerned about what, if anything, I
>> should do about this for the near term. My specific concerns are
> 
> You should rip Barracuda a new one: munging the IRT header's message-id
> violates RFC 28222 ss 3.6.4.
> 
> I would not at all recommend 'enabling' them by working around this:
> make sure that it's very clear to everyone exactly what's breaking and
> why, and whom they should contact at Barracuda to get them to stop.
> 
> "Enhanced".  Did they get bought out by Microsoft?

Jay. Just in case you did not notice:

Barracuda != BaricadeMX just like postfix != sendmail

Hugo.

- --
hvdkooij at vanderkooij.org               http://hugo.vanderkooij.org/
PGP/GPG? Use: http://hugo.vanderkooij.org/0x58F19981.asc

	A: Yes.
	>Q: Are you sure?
	>>A: Because it reverses the logical flow of conversation.
	>>>Q: Why is top posting frowned upon?

Bored? Click on http://spamornot.org/ and rate those images.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFIsuMVBvzDRVjxmYERAvyCAJ9YKYiqihir9hDpU59/gUUhguYvegCgsK5/
fDPidoHewsL2qegcSMIdnd8=
=HYF8
-----END PGP SIGNATURE-----