> I would consider the following "regular" MIME structures: > > 1. top-level MIME part is multipart/encrypted. > 2. an attached email (Content-Type = message/rfc822) containing a > multipart/encrypted MIME part as direct child.
We have been doing this in the past but changed it especially for Exchanges servers if I remember correctly, since they tend to wrap the multipart/encrypted mime part into other mime parts. Also I think it was at the Dreieich conference when I brought this issue up and was told that it is perfectly alright to have a multipart/encrypted part as a child part of other parts. It would however certainly fix this issue for PGP/MIME.
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Gnupg-users mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnupg-users
