Unfortunately, the spec doesn't actually give a way to have the dmarc record return a contact record for an actual human with a clue (and the SOA record is just as broken). I strongly suspect many of these records were pasted in once by someone who used an online dmarc record generator who then set-it-and-forget-it. "Okay, we're compliant, job done!"
I'm sure you're right which means nothing will get their attention other than their mail breaking and perhaps not even that.
We know that pct= values other than 0 and 100 never really worked, and pct=0 only made a difference for people who send mail through mailing lists and other forwarders that edit the message, which is an extrenely small fraction of all mail. (Someone at Yahoo told me that for all of the grousing about them turning on p=reject, it affected about 1% of the mail they got, albeit a 1% that the receipients felt strongly about.)
I suspect that in most cases that when we stop paying attention to pct= most of the people publishing it won't even notice. So I can't get too worked up about it.
As I've said several times, when we were revising the DMARC spec, we knew that it was unlikely that people would change their DMARC records, so for most purposes it does the same thing that the old version did.
R's, John _______________________________________________ dmarc mailing list -- [email protected] To unsubscribe send an email to [email protected]
