Ideally, Agari customers and prospects update their DMARC DNS TXT records to point to their Agari DMARC email addresses.
However, in some cases, this is not practical and their records must continue to point to their own SEG or MTA infrastructure. In this case, it is possible to forward the DMARC messages to Agari. As long as the original from header is preserved, Agari will identify the data provider and process the RUA XML or RUF message.
Why can't Agari identify the data provider using the XML itself? Why do I have to preserve the From Header?
The simple answer is it is computationally more efficient to use the From Header. Reading the XML requires parsing the email message itself, removing and opening the attachment, and then parsing the XML.
Each month, Agari processes over 4 million DMARC RUA XML Files, covering over 1.2 billion Domain and IP address pairs. And that is just from the data providers we've approved, we receive and reject data from over 4k providers.
Many of the rejected data providers are rejected because their XML is unparseable, each time we attempt to open those files we get errors. Better and more scalable to reject them at the header level.