From: Claus Färber (list-ietf-wg-apps-usefor@faerber.muc.de)
Date: Sat Oct 02 1999 - 19:00:00 CDT
Charles Lindsey <chl@clw.cs.man.ac.uk> schrieb/wrote:
> Well it wouldn't (shouldn't) say that, because message types do not have
> charset parameters.
Saying charset=unknown or saying nothing about the charset does not make
big a difference, does it?
> The fact that the type was message/news should be enough to indicate that
> the headers inside the encapsulated message should be presumed to be UTF-8
> (and if some MTA on the way has mangled them, then that is just too bad).
With the problem that MTAs _will_ mangle them:
From <ftp://ftp.sendmail.org/pub/sendmail/KNOWNBUGS>:
| * 8->7 bit MIME conversion
|
| When sendmail is doing 8->7 bit MIME conversions, and the message
| contains certain MIME body types that cannot be converted to 7-bit,
| sendmail will strip the message to 7-bit.
So even if the headers are encapsulated in the body, sendmail talking to
a host failing to announce 8BITMIME will trash it.
But it also says:
| * Null bytes are not handled properly in headers.
|
| Sendmail should handle full binary data. As it stands, it handles
| all values in the body, but only 0x01-0x80 and 0xA0-0xFF in
| the header. Notably missing is 0x00, which would require a major
| restructuring of the code -- for example, almost no C library support
| could be used to handle strings.
for headers.
-- Claus Andre Faerber <http://www.faerber.muc.de> PGP: ID=1024/527CADCD FP=12 20 49 F3 E1 04 9E 9E 25 56 69 A5 C6 A0 C9 DC