Quoting Joel W. Shea via luv-talk (luv-talk@luv.asn.au):
Possible Solution:
mailman 2.1.18 recommends using dmarc_moderation_action, instead of from_is_list from 2.1.16 [3]
* Unset the from_is_list [4] "Munge From" which causes *all* of messages sent by the list to be munged.
* Set dmarc_moderation_action [5] to one of; + Munge From - rewrite the From: and Reply-To: as in from_is_list + Wrap Message - wrap the message as in from_is_list
Which should *only* affect messages received from domains with a restrictive DMARC policy (p=reject,p=quarantine)
It seems as though this would be palatable to more people, and is probably a reason it was even implemented in 2.1.18
I'd personally prefer the latter, which preserves the original message (and header fields) in an RFC822 MIME sub-part (attachment), much like digests.
FWIW: I'd paint the bike shed the following (different) colour:
* Although wrapping the post to preserve the original header fields works, it's still a kludge, with those ugly from_is_list header fields, so I'd just reject the post(s) and send (a) sensible DMARC failure report(s) instead
* Rejecting the post, as has already been stated by others on this thread, may provide the feedback to signers (via failure reports) to determine a better "market solution"
Sounds eminently sane to me. If Yahoo mail's DMARC policy requires their domain's mail become screwed up, LUV should give it & confreres that, good and hard. -- Cheers, (morganj): 0 is false and 1 is true, correct? Rick Moen (alec_eso): 1, morganj rick@linuxmafia.com (morganj): bastard. McQ! (4x80) -- seen on IRC