I've been off this list for some time, so maybe the subject has
been beaten to death already. My excuses if so.
Also, I do understand that the IETF has no means of enforcing RFC
compliance. However the IETF is the standardization body for the
Internet and as such one could hope that a note from the IETF/IESG
may at least have some impact.
If you send a PGPencrypt:ed mail in RFC3156 ("PGP Mime") format
to a Microsoft Exchange server, the result is garbled to an extent
that programs like Thunderbird/Enigmail can no longer cope with it.
RFC3156 Example message:
Content-Type: multipart/encrypted; boundary=foo;
protocol="application/pgp-encrypted"
...
Exchange version:
Content-Type: multipart/mixed; boundary=bar;
...
So, Exchange converts the message "type" (Mime top level) from
something that is quite well defined (multipart/encrypted) to
something that can be almost anything (multipart/mixed).
Two URLs:
http://social.technet.microsoft.com/Forums/en-US/exchangesvrtransport/thread/0f90b1be-6e7e-4658-b577-2bcfec02f7c9
http://mozilla-enigmail.org/forum/viewtopic.php?f=4&t=425
Gunnar Lindberg
Exchange version, slightly more complete. The base64 encoded parts
contain the original mail. The base64 encoding is annoying but much
worse is that those parts are fairly much out of context.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
From: xxx <x@y>
To: xxx <x@y>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary=bar;
--bar
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
--bar
Content-Type: application/pgp-encrypted;
name="PGPMIME version identification"
Content-Description: PGP/MIME version identification
Content-Disposition: attachment;
filename="PGPMIME version identification";
size=76; creation-date="Fri, 03 Jul 2009 15:35:18 GMT";
modification-date="Fri, 03 Jul 2009 15:35:18 GMT"
Content-Transfer-Encoding: base64
VmVyc2lvbjogMQ0K
--bar
Content-Type: application/octet-stream; name="encrypted.asc"
Content-Description: OpenPGP encrypted message.asc
Content-Disposition: attachment;
filename="encrypted.asc"; size=2044;
creation-date="Fri, 03 Jul 2009 15:35:18 GMT";
modification-date="Fri, 03 Jul 2009 15:35:18 GMT"
Content-Transfer-Encoding: base64
LS0tLS1CRUdJTiBQR1Ag ...
--bar--
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
_______________________________________________
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf