Author pitrou
Recipients Dmitry.Jemerov, giampaolo.rodola, ncoghlan, pitrou, r.david.murray
Date 2010-09-23.16:56:45
SpamBayes Score 0.000102108
Marked as misclassified No
Message-id <1285261007.95.0.209682595913.issue9360@psf.upfronthosting.co.za>
In-reply-to
Content
Yes, unescaped utf-8 is explicitly allowed in headers by RFC 3977:

   The content of a header SHOULD be in UTF-8.  However, if an
   implementation receives an article from elsewhere that uses octets in
   the range 128 to 255 in some other manner, it MAY pass it to a client
   or server without modification.  Therefore, implementations MUST be
   prepared to receive such headers, and data derived from them (e.g.,
   in the responses from the OVER command, Section 8.3), and MUST NOT
   assume that they are always UTF-8.

(I guess this means NNTP is now more modern than SMTP :-)).

Actually, there's a test with an actual utf-8 header in the unit tests.
(as for “implementations MUST be prepared to receive such headers, and data derived from them”, this is accounted for by using surrogateescape).
History
Date User Action Args
2010-09-23 16:56:49pitrousetrecipients: + pitrou, ncoghlan, giampaolo.rodola, r.david.murray, Dmitry.Jemerov
2010-09-23 16:56:47pitrousetmessageid: <1285261007.95.0.209682595913.issue9360@psf.upfronthosting.co.za>
2010-09-23 16:56:46pitroulinkissue9360 messages
2010-09-23 16:56:45pitroucreate