[Mailman-Developers] Re: Cutting "Received:" headers (John A. Martin)

[John A. Martin]

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

>>>>> "Tom" == Tom Neff
>>>>> "[Mailman-Developers] Re: Cutting "Received:" headers (John A. Martin)"
>>>>>  Wed, 11 Jun 2003 12:57:09 -0400

    Tom> jam at jamux.com (John A. Martin) wrote:
    >> [Roman Sinelnikov wrote:]
    >>> Dear colleagues, one more idea, it would be very convenient to
    >>> have an optional cutting of "Received:" headers in any e-mail
    >>> message before its sending by Mailman to the list members.
    >>
    >> Rfc2822 Section 3.6.6

    Tom> Concise, but wrong for the following reasons.

    Tom> 1. "Received:" is a Trace field, not a Resent field, and
    Tom>     hence is covered in RFC 2821, not 2822:

Indeed.  I was too quick and my eyes too dim.

Without going back for chapter and verse it is my understanding that
if you change the Message-ID field you may start a new trace but that
if you do not change the Message-ID you should only add to the trace.

Without changing the Message-ID it does not seem that a respectable
mailing list should do anything more than append to the end on the
body of a mail message.  If a moderator edits a message it should be a
new message.  Some will drop MIME parts.  I would reject the mail
rather than change it.

For example, I PGP sign all non-trivial mail and have done so for
years to establish plausible deniability for mail without my PGP
signature.  If I discover that a PGP signed mail of mine has been
altered I will disclaim all responsibility for it.  If that were to
happen repeatedly on a mailing list I would object to my mail being
altered an I would withdraw from the list.  I have not known this to
happen however.

        jam

-----BEGIN PGP SIGNATURE-----

iD8DBQE+53mwUEvv1b/iXy8RApUDAJ9yrrjU3HEX+bDcUp3UEK1D03ImPwCbBoXM
f4L3hRmP8w3l7sOYZD09ldU=
=hsx8
-----END PGP SIGNATURE-----