John R. Levine:
> > 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?
Once you allow non-ascii headers, you break compatibility with
existing infrastructure, so you break other things to work around
it (with "you" not specifically aimed at John R. Levine, btw). For
security's sake I'd prefer if they had broken the 8bit header rule
instead of MIME.
Wietse
