Yeah, Yahoo has been doing this DMARC denial for a while, it is problematic for listservs especially, but also things like emails generated by web site contact forms depending on how they are setup to send. One work-around is the mitigation of changing the FROM: header and adding a Reply-To: header. That way replying to the list message could still go back to the originally sender, but DMARC won't block because the FROM: doesn't result in a match. The From: header could even show the aol/yahoo email address in "Name" part of that header and still get past dmarc blocks... Yahoo listservs follow that style themselves. Example: From: "useremail at aol.com [hidden-tech]" <hidden-discuss at lists.hidden-tech.net> Reply-To: useremail at aol.com Charles Strader ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Worker-Owner at Gaia Host Collective http://gaiahost.coop For General Support: support at gaiahost.coop or phone x0 On 4/26/15 11:49 PM, R. David Murray wrote: > > > The problem is that the mailing list wants to re-send the message as > 'from' the aol address, but with various bits of the message modified. > DMARC disallows this. > > This is a known problem and has been for quite some time with Yahoo at > least. There are various articles about it. Mailman (the most popular > mailing list software) has some mitigations for it that the list owner > can select, but I don't think any of them are perfect. I know of > at least one site that just rewrites the from address so that it > is no longer a yahoo address (xyz at yahoo.com.dmarc-invalid), which > at least allows the message to be delivered. Also not a very > good solution. > >