>> Block any attempt to post to a mailing list from a domain that >> publishes strict DMARC. That doesn't affect functionality for >> legitimate users and it complies with the domain owners >> wishes (however misguided). > >That's clever, and oddly constructive. It informs the user of the issue >at exactly the right time: when the subscription is being attempted and >the user is focused on the possibility of the subscription having >problems. Much better than indirect and obscure notification later, >after posting a message.
Steve actually said when people try to post. I tried that, since it's one line in the config in my list manager. It caught a bunch of mail from real people going to real lists (the church lists are busy, the minister just said he's retiring) and I would not look forward to explaining to people why their mail account that has worked fine for a decade can't reply and say whether they're coming to this afternoon's meeting. So I did the redacted From: line which was slightly harder, but moves the pain slightly while still encouraging people to find a new address. R's, John _______________________________________________ dmarc-discuss mailing list [email protected] http://www.dmarc.org/mailman/listinfo/dmarc-discuss NOTE: Participating in this list means you agree to the DMARC Note Well terms (http://www.dmarc.org/note_well.html)
