Mailman-coders

Download

mailman-coders@python.org

June 2017

7 participants
41 discussions

[Bug 1643210] [NEW] 'from_is_list' does not RFC2047 encode correctly when translation contains non-ascii char
by Yasuhito FUTATSUKI＠POEM 02 Jun '17

02 Jun '17

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 Importance: Undecided Status: New ** Attachment added: "CookHeaders.py.diff.txt" https://bugs.launchpad.net/bugs/1643210/+attachment/4780159/+files/CookHead… ** 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. https://bugs.launchpad.net/bugs/1643210 Title: 'from_is_list' does not RFC2047 encode correctly when translation contains non-ascii char To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1643210/+subscriptions

2 16