[Bug 1539384] Re: Non-blocking DMARC mitigations should also be done for p=none

[Mark Sapiro]

If I understand correctly, what you are saying is that by publishing
DMARC p=none you receive reports of Mailman list mail that fails DMARC
and some of these reports MIGHT be spurious because if your DMARC policy
were quarantine or reject the lists MIGHT apply Mailman's DMARC
mitigations.

I will consider addressing this, but not in the way you suggest. I will
consider adding another list setting dmarc_none_moderation_action -
Shall the above dmarc_moderation_action if Munge From or Wrap Message
apply to messages From: domains with DMARC p=none as well as p=reject
and  p=quarantine? with the more detailed help explaining that a Yes
setting only makes sense if dmarc_quarantine_moderation_action is also
Yes and also explaining that the intend is to suppress the reports to
the domain owner of failures that wouldn't be failures if the domain
owner's policy were quarantine or reject.

I will not do this unconditionally because I believe it should be up to
the individual list owner to decide whether she wants Munge From or Wrap
Message applied to messages that should be accepted without these
transformations.


** Changed in: mailman
       Status: Won't Fix => Triaged

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

Title:
  Non-blocking DMARC mitigations should also be done for p=none

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