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

Mark Sapiro mark at msapiro.net
Fri Jan 29 00:33:58 EST 2016

I think I see what you are saying. If I have it right, you admin a
domain that publishes DMARC p=none to get reports to assess the effect
of going to a stronger DMARC policy, but you see reports due to Mailman
list mail because Mailman does not apply DMARC mitigations to mail From:
domains that publish DMARC p=none. So you would like Mailman to apply
disruptive message transformations to mail From: your domain that would
be transformed if you applied a stronger DMARC policy.

My opinion is DMARC and mailing lists do not play well together. DMARC
was originally intended to be used by domains such as those of financial
institutions where mail From: those domains would only be for business
purposes and not posted by individuals to mailing lists. It was mis-used
by Yahoo and later AOL in a misguided attempt to make upo for prior
security lapses, but was never intended to be used by domains that
provided email service to users for personal use.

While I don't understand what your domain is or what it is used for, I
suggest that if individuals are allowed/encouraged to send personal mail
From: your domain to email lists, that DMARC p=quarantine or p=reject
policies are inappropriate.

** Changed in: mailman
   Importance: Undecided => Wishlist

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

You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.

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

To manage notifications about this bug go to:

More information about the Mailman-coders mailing list