DMARCIAN: What is “External Destination Verification”?

DMARCIAN just posted another brilliant article:

A domain’s DMARC record can tell the world to send DMARC reports to a different domain. For example, the domain example.org might have a DMARC record of: v=DMARC1; p=none; rua=mailto:dmarc_reports@sample.net This DMARC record tells people to send reports regarding example.org to the email address of dmarc_reports@sample.net. Before reports are sent, sample.net must tell the world that it is OK to send example.org’s reports to sample.net. Otherwise, reports will not be sent to sample.net. Allowing “external” domains to accept DMARC reports is called “External Domain Verification.” For those who like too much information, the DMARC RFC describes in detail how report generators determine if sample.net is allowed to receive reports related to example.org. External Domain Verification is made possible when sample.net publishes a special TXT record at a specific location in the DNS. If example.org tells the world to send DMARC reports to the sample.net domain, people who are sending reports will

Continued here: What is “External Destination Verification”?

P.S. Do you need help with Email Authentication? Ask for a Consultation