[Bug 1536816] [NEW] Mailman can create a non-ascii or improperly RFC 2047encoded From: header.

Mark Sapiro mark at msapiro.net
Thu Jan 21 17:36:13 EST 2016


Public bug reported:

When creating the new From: header for a message with from_is_list or
dmarc_moderation_action set to Munge From or Wrap Message, if the
incoming From: has no display name so Mailman gets the display name from
the poster's list member data, and that name contains non-ascii, Mailman
puts the non-ascii display name in the new From: header and subsequent
processing can see the non-ascii and attempt to RFC 2047 encode it, but
do that improperly.

** Affects: mailman
     Importance: Medium
     Assignee: Mark Sapiro (msapiro)
         Status: Fix Committed

** Summary changed:

- Mailman can create a non-ascii or improperly RFC 2047encoded From" header.
+ Mailman can create a non-ascii or improperly RFC 2047encoded From: header.

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1536816

Title:
  Mailman can create a non-ascii or improperly RFC 2047encoded From:
  header.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1536816/+subscriptions


More information about the Mailman-coders mailing list