[Bug 1643210] [NEW] 'from_is_list' does not RFC2047 encode correctly when translation contains non-ascii char
Yasuhito FUTATSUKI at POEM
futatuki at poem.co.jp
Sat Nov 19 12:07:50 EST 2016
Public bug reported:
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)
** Affects: mailman
** Attachment added: "CookHeaders.py.diff.txt"
** Branch linked: lp:mailman/2.1
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
'from_is_list' does not RFC2047 encode correctly when translation
contains non-ascii char
To manage notifications about this bug go to:
More information about the Mailman-coders