in draft-ietf-eai-rfc5335bis-12.txt. While Victor is too specific about message/rfc822, the draft explicitly allows transfer-encoding of message/global, which is just as problematic as allowing message/rfc822 non-identity encoding.
Yes, it does, although that's the best of a bad lot. People are going to send EAI messages as attachments, some of the mail they're attaching it to will be 5322. What else could they do? Tell people to hide them inside base64 encoded zip files?
Really, they went through every option you can possibly think of to make EAI mail somewhat more backwards compatible, and they all went down ratholes, so they stripped it all out and made EAI a separate parallel mailstream to 5321/5322
See my three-part blog entry at http://jl.ly/Email/i18n.html Regards, John Levine, jo...@iecc.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. http://jl.ly
