Wout Mertens wrote: > Hi there, Hi, > > 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: > > Original: > Subject: =?ISO-2022-JP?Q?607716139:_=1B$B%a%C%;!<%8%m%1!< > %=3FF0:nIT6q9g=1B(B?= > > Mailman-sent: > Subject: =?ISO-2022-JP?Q?607716139:_=1B$B%a%C%; !<%8%m%1!< > %=3FF0:nIT6q9g=1B(B?=
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? > > Thanks! > > Wout. Cheers, -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ _______________________________________________ Mailman-i18n mailing list Posts: [email protected] Unsubscribe: http://mail.python.org/mailman/options/mailman-i18n/archive%40mail-archive.com
