Greg writes:
This is a 8 bit text entity in the headers of the message part, the
headers of the body part need to be encoded in quoted printable, which
is prohibited.
Well, the header fields need to be encoded, not the names. This is not
specifically prohibited, nor is it specifically permitted.
Rewritten to make this more clear....
From: <ASCII form>
Subject: <ASCII form>
Content-type: message/iso-8859-2
From: <iso-8859-2-form> * Untransportable
Subject: <iso-8859-2-form> * Untransportable
Content-type: text/iso-8859-2
Content-Encoding: Quoted-Printable
Message body in iso-8859-2 character set.
Where the Content-encoding really is intended to apply to the
headers as well as the body of the part. Problem is, how to read the
headers to find the encoding if they are encoded!
The RFC-XXXX header-names and header-fields must be ASCII, so you will be
able to find the encoding. The problem is how to know that the encoding
applies to the accompanying 822 headers. And if the Content-Encoding is
Base64 it could get really ugly. There could be a rule that states that
all 822 header fields in encapsulated messages must be encoded using
Quoted-Printable.
Jim