> Any thoughts?!??! Yes.
One: This would be better directed at the dmarc-discuss list, which deals with operational issues vs. specification issues. See http://www.dmarc.org/mailman/listinfo/dmarc-discuss for list details or subscription. I'd take the follow-ups there. Two: The minimum record for your domain would be "v=DMARC1; p=none; rua=mailto:[email protected]"; -- if you must keep your domain secret, it may be instructive to lose the other options and see what happens. Three: You should share the actual domain which is seeing the problem. You're interested in how AOL sees and reacts to your records -- how are they to check what their systems see, which could differ from where ever you ran your queries? Nor can anybody else lookup what their systems see happening for your domain, as things stand. Perhaps XS4ALL sees the problem and knows the cause, but you've avoided that possibility coming to light. --S. On Thu, Apr 3, 2014 at 9:50 AM, McNamee, Tom <[email protected]> wrote: > I implemented DMARC on a production sending domain a few months ago. I > have received daily aggregate reports from Comcast, Google, yahoo, hotmail, > 163.com, 126.com, and mail.ru. I have not received a single DMARC report > from AOL. > > > > Here are my DNS records: > > > > ## dig txt _dmarc.<dmarc_sending.domain> > > _dmarc.<dmarc_sending.domain>. 3575 IN TXT > "v=DMARC1\; p=none\; pct=100\; > rua=mailto:<address_on_domain-receiving-reports>\; > sp=none\; adkim=r\; aspf=r" > > > > ## dig txt > <dmarc_sendng.domain>._report._dmarc.<domain-receiving-reports>. > > <dmarc_sendng.domain>._report._dmarc.<domain-receiving-reports>. 13890 > IN TXT "v=DMARC1" > > > > Any thoughts?!??! > > > > Thanks! > > -Tom > > _______________________________________________ > dmarc mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dmarc > >
_______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
