In <200204300031(_dot_)g3U0VCe23848(_at_)astro(_dot_)cs(_dot_)utk(_dot_)edu>
Keith Moore <moore(_at_)cs(_dot_)utk(_dot_)edu> writes:
also, even if transports are "munge free", that doesn't mean that they
can parse utf-8 headers correctly. and various kinds of transports
do parse headers.
OK, so which headers do transports need to parse?
The address headers presumably (either to construct the envelope as in
'sendmail -t', or in transports like uucp which use the To and Cc headers
directly).
The Received header (well, generate rather than parse).
Maybe the Date (for logging)
But I doubt they need to parse Message-ID, References, and the like,
except so far as is needed to extract a unique string of octets for
logging. Anyway, I would recommend insisting on strict ASCII within
msg-ids.
So let us identify the cases and see what troubles might ensue.
--
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131 Fax: +44 161 436 6133 Web: http://www.cs.man.ac.uk/~chl
Email: chl(_at_)clw(_dot_)cs(_dot_)man(_dot_)ac(_dot_)uk Snail: 5
Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9 Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5