https://bugs.kde.org/show_bug.cgi?id=360205
--- Comment #9 from Pali Rohár <pali.ro...@gmail.com> --- On Monday 07 March 2016 13:17:45 Erik Quaeghebeur via KDE Bugzilla wrote: > https://bugs.kde.org/show_bug.cgi?id=360205 > > --- Comment #7 from Erik Quaeghebeur <kdeb...@equaeghe.nospammail.net> --- > (In reply to Pali Rohár from comment #5) > > On Monday 07 March 2016 12:31:08 Erik Quaeghebeur via KDE Bugzilla wrote: > > > line-breaks in subjects are not allowed. > > > > Hm... is there restriction in RFC for this? Just asking. > > In RFC 5322, it is said that Subject is an unstructured field, which is > described in Section 2.2.1 as > > « Some field bodies in this specification are defined simply as > "unstructured" (which is specified in section 3.2.5 as any printable > US-ASCII characters plus white space characters) with no further > restrictions. These are referred to as unstructured field bodies. > Semantically, unstructured field bodies are simply to be treated as a > single line of characters with no further processing (except for > "folding" and "unfolding" as described in section 2.2.3). » > > More generally, as far as I've understood (and modulo folding), a header value > MUST NOT contain any line breaks. > This is truth, but RFC 2047 allows you to include any unicode character into header body (via encoding unicode character to UTF-8 and encoding it to either QP or Base64). It means that also newline can be encoded into Base64. From RFC 5322 point of view, Base64 is single line (after unfolding) but you have funny unicode and also ascii whitespaces in header body... Or is there some restriction that above is violation of MIME or something else? -- You are receiving this mail because: You are watching all bug changes.
