'from_is_list' does not RFC2047 encode correctly when translation contains non-ascii char
Bug #1643210 reported by
Yasuhito FUTATSUKI at POEM
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNU Mailman |
Fix Released
|
High
|
Mark Sapiro |
Bug Description
If from_is_list feature is used, From: header's `realname' field is composed by original realname
and translation of '%(realname)s via %(lrn)s' which may contain non-ascii character.
The realname field is encoded before compose if nessesary, but translation part is not.
So From header may contain raw non-ascii character.
To fix this, do RFC 2047 encode after compose.
(There is another bug..., if servers language setting and mail list preferred language is differ,
translation has taken from servers language, not from mail list one. Attached patch contains
fix of it)
Related branches
Changed in mailman: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
My #1 patch try to adjust to charset/encoding list's preferred. But after I realize my misunderstanding, it is better to adjust to sender's preference. Anyways original senders `realname' charset and translation of '%(realname)s via %(lrn)s' charset and list's preference can differ each other.