https://bugs.kde.org/show_bug.cgi?id=360205
--- Comment #10 from Erik Quaeghebeur <kdeb...@equaeghe.nospammail.net> --- (In reply to Jan Kundrát from comment #8) > > More generally, as far as I've understood (and modulo folding), > > a header value MUST NOT contain any line breaks. > > There is RFC2047 which specifies how to send Unicode. It gets triggered by > presence of LFs in my testing, and I think that this usage is actually > kosher -- but i'll be happy to be proven wrong by a quite from some other > RFC. The token definition in RFC822 that allowed bare CR and bare LF was updated in RFC2822 to preclude them: RFC2047 Section 5. (1) on p.7: « An ’encoded-word’ may replace a ’text’ token (as defined by RFC 822) in any Subject or Comments header field [...] » RFC822 Section 3.3 on p.10: « text = <any CHAR, including bare CR & bare LF, but NOT including CRLF> » RFC2822 Section 3.2.1 on p.10: « text = %d1-9 / %d11 / %d12 / %d14-127 / obs-text ; Characters excluding CR and LF » (RFC5322 doesn't reintroduce them.) So digesting them is needed for dealing with old messages, but producing them is, in my understanding, against the latest RFC. -- You are receiving this mail because: You are watching all bug changes.
