[Mailman-i18n] Problem with header encoding on 2.1.9 - any ideas?
wmertens at cisco.com
Fri Jan 18 14:50:17 CET 2008
many thanks for your swift reply!
Looking further at this, I also found a header that wasn't impacted by
this, but it wasn't encoded either. This header is the same in both
original and mailman-processed mails:
note the second line, there the ";" is without a space.
So it seems to me that MailMan only changes certain headers? Do you
think there's an easy way to configure MailMan to leave the Subject
On Jan 18, 2008, at 1:40 AM, Tokio Kikuchi wrote:
> Wout Mertens wrote:
>> Hi there,
>> I have a problem with MailMan and Japanese ISO-2022-JP encoding.
>> When a header includes a ";" as part of the ISO-2022-JP encoding,
>> MailMan seems to replace it with "; " (note the extra space). This
>> messes up the characters.
>> Real-life example:
>> Subject: =?ISO-2022-JP?Q?607716139:_=1B$B%a%C%;!<%8%m%1!<
>> Subject: =?ISO-2022-JP?Q?607716139:_=1B$B%a%C%; !<%8%m%1!<
> This is because the python email package can't distinguish between
> structured and un-structured RFC2822 headers. The Q-encoded
> iso-2022-jp string contains ';' character which cause the email
> package to think it is a syntactic separator, thus insert a space.
> Most Japanese capable mailers use B-encoding to avoid such confusion.
> Workaround is rather tricky but try add a subject_prefix like
> [listname] on the admin interface which may trigger normalization by
> the Mailman CookHeader module.
>> I tried looking at the code, but I couldn't figure it out and so
>> I'm asking here first before I dig deeper. Does anybody know what
>> might cause this?
> Tokio Kikuchi, tkikuchi at is.kochi-u.ac.jp
More information about the Mailman-i18n