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

[Hugo van der Kooij]

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

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).

Simply put.

If I detect headers like:
In-Reply-To:
<EMEW-k7NDHP5cf949af6a11121e8aeab488ab3371ce-48B1509C.8050409 at vanderkooij.org>

Or:
References:
<EMEW-k7NDHP5cf949af6a11121e8aeab488ab3371ce-48B1509C.8050409 at vanderkooij.org>

It is safe to assume someone has been tampering with my message
Identifiers. And I am entitled to block those as RFC violations.

That should not be to hard to build into postfix.

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)

iD8DBQFIskfRBvzDRVjxmYERAmClAJ9C40J8KyadINm+WBf47JyCk1LSNwCgiXym
w3LBRSxwM6YobBNfkXQsqfk=
=ehPv
-----END PGP SIGNATURE-----