[Bug 1582819] Re: subject encoding bug

[Mark Sapiro]

=?ISO-8859-2?Q?PIVOT_kutat=E1sfinan?=
=?ISO-8859-2?Q?sz=EDroz=E1si_adatb=E1zi?=s

is still non-compliant.

It is too long: RFC2047 section 2 says in part

   While there is no limit to the length of a multiple-line header
   field, each line of a header field that contains one or more
   'encoded-word's is limited to 76 characters.

but that is not the issue here. The issue is the same as before. The
final 's' is not separated from the preceding encoded word by linear
white space. If the header were

Subject: =?ISO-8859-2?Q?PIVOT_kutat=E1sfinan?=
 =?ISO-8859-2?Q?sz=EDroz=E1si_adatb=E1zi?= s

Mailman would produce

Subject: [List1] =?iso-8859-2?q?PIVOT_kutat=E1sfinansz=EDroz=E1si_adatb=E1?=
 =?iso-8859-2?q?zi_s?=

which is not quite what you want as it decodes to

Subject: [List1] PIVOT kutatásfinanszírozási adatbázi s

and you presumably want 'adatbázis', not 'adatbázi s'. There are always
whitespace issues when mixing encoded words and plain text in one
header. The proper encoding of that header is

Subject: =?ISO-8859-2?Q?PIVOT_kutat=E1sfinan?=
 =?ISO-8859-2?Q?sz=EDroz=E1si_adatb=E1zis?=

Granted, various MUAs are more forgiving of the defects, but the Mailman
issue is really in the underlying Python email package which insists
that the terminating ?= be followed by white space in order that the
encoded word be recognized as such.


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

-- 
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