[Bug 1643210] Re: 'from_is_list' does not RFC2047 encode correctly when translation contains non-ascii char

Mark Sapiro mark at msapiro.net
Sun Nov 20 13:09:36 EST 2016

I'm having trouble understanding what the problem is. There are 3
possible sources of realname. In order of preference, the display name
in the message's From: header if any; if not and the From: address is a
list member, the list member's username if any, and if not, the local
part of the sender's email address.

In the first case, the real name should already be RFC 2047 encoded in
the incoming message and that will be the resultant value in the munged
From: header. In the other cases if the name contains non-ascii, it will
be RFC 2047 encoded in the character set of the list's preferred
language (or maybe utf-8 if the real name is a unicode).

It seems all this should be OK.

Please provide and actual From: header and possibly relevant list
settings that illustrate the problem.

Or is the issue that the list's real_name (lrn in the code)is not rfc
2047 encoded. I see that, but I think the fix is simply to replace the
one line

lrn = mlist.real_name


lrn = str(uheader(mlist, mlist.real_name))

** Changed in: mailman
       Status: New => Incomplete

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 mailing list