[Bug 1582819] Re: subject encoding bug

[Mark Sapiro]

I am unable to duplicate exactly what you describe, but I do see an
issue in that this:

Subject: =?ISO-8859-2?Q?Part_=31_?==?ISO-8859-2?Q?Part_=32_?=

gets changed to

Subject: [List1]
=?iso-8859-2?q?Part_1_=3F=3D=3D=3FISO-8859-2=3FQ=3FPart_2?=

however the incoming Subject is non-compliant. RFC2047 section 5(1) says
in part:

Ordinary ASCII text and 'encoded-word's may appear together in the same
header field.  However, an 'encoded-word' that appears in a header field
defined as '*text' MUST be separated from any adjacent 'encoded-word' or
'text' by 'linear-white-space'.

If I add a space as in

Subject: =?ISO-8859-2?Q?Part_=31_?= =?ISO-8859-2?Q?Part_=32_?=

the result is

Subject: [List1] =?iso-8859-2?q?Part_1_Part_2?=

which is correct.

If you see this issue with an RFC 2047 compliant encoded Subject: or
other header, pleas provide the exact header that causes the issue.

** Changed in: mailman
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1582819

Title:
  subject encoding bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1582819/+subscriptions