[Mailman-Users] Handling Munged From Addresses

Dennis Putnam dap1 at bellsouth.net
Thu Feb 27 14:54:33 EST 2020

On 2/27/2020 1:38 PM, Mark Sapiro wrote:
> On 2/27/20 10:17 AM, Dennis Putnam wrote:
>> Thanks for the reply. I am not seeing that. The From: looks like this:
>> From: Rushtalk Discussion List via Rushtalk <rushtalk at csdco.com>
> That must be a RedHat thing having to do with their backport of DMARC
> mitigations. If you don't like it, install from source.
>> In "General Options" for that list I set the item "Replace the From:
>> header address with the list's posting address to mitigate issues
>> stemming from the original From: domain's DMARC or similar policies."
>> with "Munge From." Did I set the wrong thing?

> That will apply From: munging to all posts. I have no idea what the
> RedHat package does, but if in Privacy options... -> Sender filters you
> have dmarc_moderation_action and dmarc_quarantine_moderation_action set
> General Options -> from_is_list to No and set dmarc_moderation_action to
> Munge From and dmarc_quarantine_moderation_action to Yes and if you have
> it, dmarc_none_moderation_action to No.
> This will apply From: munging only to those messages From: a domain that
> publishes DMARC policy = reject or quarantine.
Hi Mark,

I didn't realize that there were OS dependencies in the DMARC
mitigation. I thought it was all within the mailman code.

In any case I'll look through those options and see what they do in
RHEL. Thanks.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20200227/503774a5/attachment.sig>

More information about the Mailman-Users mailing list