Re: A permission to re-sign header
Michael Richardson <[email protected]> Sat, 19 Apr 2014 09:05:23 -0400
| Newsgroups | gmane.ietf.rfc822 |
|---|---|
| Message-ID | <[email protected]> |
John R Levine <[email protected]> wrote: >> First of all, "permission to re-sign" seems to me to be the wrong >> semantics. This is simply "originally sent from here to there". The >> originating site (example.com) wants to say, "This message came from >> example.com and got sent to [email protected]", in a way that >> someone who receives a message from foo.example.net can check. > It has to be more than that, it has to say that it's OK for foo.example.net > to pass it along in modified form. Yes, in particular, it's quite likely both DKIM and S/MIME signatures will not survive some things the mailing list might want to do, including: 1) removing html parts or other attachments 2) formatting html part to text/plain 3) formatting text/plain; format=outlook into proper format=flowed -- Michael Richardson <[email protected]>, Sandelman Software Works -= IPv6 IoT consulting =- _______________________________________________ ietf-822 mailing list [email protected] https://www.ietf.org/mailman/listinfo/ietf-822
signature.asc
(application/pgp-signature, 307 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQCVAwUBU1J0k4qHRg3pndX9AQILPQP/SSVp1SkzyjRINskvwKqIyxFmC0BsFleB jpUw8UE7gIAxMwL6FHq4QflB3Jcq0z56cbQ/VbcgwJCCEJ4zWbJ4bYMcEdv8xLPG ZcgqXKsfnSC0d6J4QMzbkru/8UJeYLTjf14ofMbOdMlqONzPuabrUTDVr2q0FORL W6Y9pz5P5zw= =eF0e -----END PGP SIGNATURE-----