DMARC Wrap Message doesn't preserve addressees
We've noticed that with DMARC moderation set to "Wrap Message", the rewritten header doesn't preserve the original addressee list. In the particular case that I'm looking at right now, the list address itself is removed from the Cc header. We've had a few complaints that this results in responses not going back to the list, as intended.
I don't see a related config option, but I'm wondering if I've missed something. Is this possibly the side-effect of, or an undesirable interaction with, some other configuration option we might have set?
We're running v2.1.38.
Thanks
On 2/28/22 15:41, Matthew Pounsett wrote:
We've noticed that with DMARC moderation set to "Wrap Message", the rewritten header doesn't preserve the original addressee list. In the particular case that I'm looking at right now, the list address itself is removed from the Cc header. We've had a few complaints that this results in responses not going back to the list, as intended.
Wrap message is intended to send the original message wrapped in an outer message from the list. This is something akin to a MIME format digest containing only one message.
Replying to the message works best if you can open the message/rfc822 message part which is the original message and reply to that. That said, not all MUAs make that easy or even possible.
The wrapper itself will only copy the To:, In-Reply-To:, References:, Subject:, X-Mailman-Approved-At: and Date: headers from the wrapped message. In addition, it will include any headers that were set or modified by the CookHeaders handler. These include X-Ack:, X-BeenThere:, X-Mailman-Version:, Precedence:, List-Id: and From: and may or may not include X-Ack:, Reply-To: and Cc: depending on various list settings and message characteristics. See remarks beginning at https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman/... and https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman/... for things that affect this.
I don't see a related config option, but I'm wondering if I've missed something. Is this possibly the side-effect of, or an undesirable interaction with, some other configuration option we might have set?
There is no configuration setting per se. The bottom line is the original Cc: will not be in the wrapper in many cases.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Mon, Feb 28, 2022 at 9:23 PM Mark Sapiro mark@msapiro.net wrote:
message characteristics. See remarks beginning at https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman/... and https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman/... for things that affect this.
The logic there is a bit complex, so let me see if I've got this straight ... if I set reply_goes_to_list to 1, and the message already has a reply_to, the list address would be appended to that header? Or replace it? It's not entirely clear to me.
On 2/28/22 19:25, Matthew Pounsett wrote:
The logic there is a bit complex, so let me see if I've got this straight ... if I set reply_goes_to_list to 1, and the message already has a reply_to, the list address would be appended to that header? Or replace it? It's not entirely clear to me.
If first_strip_reply_to is Yes, the list address will replace the Reply-To. If it is No, the list address will be added to the Reply-To.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro -
Matthew Pounsett