DMARC munge action breaks CC: header with full personalization
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNU Mailman |
Fix Released
|
Medium
|
Mark Sapiro |
Bug Description
If you use full personalization, the resulting headers on a message usually look like:
From: Sender <email address hidden>
To: Recipient <email address hidden>
Cc: <email address hidden>
Note the "Cc:" (added by Mailman/
If a DMARC munge happens, Mailman/
msgdata[
However, CookHeaders.py at line 202 later notices that and fails to add the Cc: header because of it.
Because of this, the headers of a munged message, for example, will look like:
From: Sender via list <email address hidden>
Reply-To: Sender <email address hidden>
To: Recipient <email address hidden>
There is no "Cc:" header present at all, and popular clients like Gmail don't offer recipients a "Reply to All" choice for DMARC-munged messages.
It seems that when using full personalization, the Cc: header should appear whether or not the From and Reply-To were munged due to DMARC.
(I have manually verified that if the Cc: header was present -- that is, if the munged headers looked like this:
From: Sender via list <email address hidden>
Reply-To: Sender <email address hidden>
To: Recipient <email address hidden>
Cc: <email address hidden>
... then Gmail would correctly offer both "Reply" and "Reply to All" options and send them to the right places.)
Related branches
Changed in mailman: | |
status: | In Progress → Fix Released |
Thanks for your report and detailed analysis. I'll fix it soon.
Actually, the Cc: has nothing to do with 'reply to list'. That's based on the RFC 2369 List- headers, but I see the issue if the list address is only in From: which is superceded by Reply-To: