On Sun, Feb 7, 2016 at 12:22 PM, John Levine via dmarc-discuss < dmarc-discuss@dmarc.org> wrote:
> In article <CAGGEJxZq-y455dJ6USs5LNqbmT= > lpssuf90dwnrzk2kutpx...@mail.gmail.com> you write: > >The mailing list question can be a bit tricky. > > No kidding. Here's a more complete set of workarounds we put on > the ASRG wiki. > > http://wiki.asrg.sp.am/wiki/Mitigating_DMARC_damage_to_third_party_mail > > I rewrite DMARC'ed addresses to local forwarding addresses and add a > DKIM signature in the forwarding domain, since of all the proposed > workarounds it seems to do the least damage to the users of the > mailing list. For example. mail from mari...@yahoo.com turns into > mari...@yahoo.com.dmarc.fail. > > Except that @yahoo.com.dmarc.fail is not a domain that exists, and will negatively impact the email deliverability. Basically, it is no better than using cousin domains to phish receivers... A real false good solution.
_______________________________________________ dmarc-discuss mailing list dmarc-discuss@dmarc.org 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)
