Re: More on forwarding quoted-printable encoded messages

[Steinar Bang <sb@metis.no>]

>>>>> "Bjørn Mork" <bmork@dod.no>:

> I believe the forwarded message should be unchanged even if the it
> violates RFC2046/7 e.g. by using 8bit headers. The message/rfc822
> CTE would then be 8bit if the original message, including headers,
> contains any 8bit chars, otherwise 7bit. RFC2046 does not require
> the forwarded message to comply with RFCs 2046-49. It even
> explicitly states that the body of a message/rfc822 part does not
> need to be RFC822-conformant! How do you encode the forwarded
> message if it contains 8bit characters but no CT/CTE headers? Isn't
> it better not to make any charset and encoding choice for the final
> recipient, and therefore forward the message untouched?

Well, the fact of the matter is that the current approach (c-t-e q-p
on the message/rfc822 part) breaks when read in Gnus 5.8.x, Netscape,
Outlook98, and OE, if the message you're forwarding contains non
US-ASCII characters.

Complying with RFC-2046 seems to me, like a step towards un-breaking
Gnus forwarding.

I see interoperability with other mail agents for the messages I am
forwarding these days (text/plain; charset=iso-8859-1, c-t-e q-p or
8bit) as more important than correct transfer of hypotethical non-MIME
messages with 8bit characters.