Reading DMARC reports – how to see who sends emails in your name
You have set up a DMARC record with a report address, and now emails with attachments from Google, Microsoft and others arrive every day. They tell you which servers sent emails in your name and whether those passed the check. Here I show how to read the reports and what to do with them.
How the DMARC record itself is built is explained in SPF, DKIM and DMARC explained. The reports are the reason to start with p=none: they show what would happen before you let anything be filtered out.
What a report contains
The reports sent to the address after rua= are called aggregate reports. Each large recipient usually sends one a day, as an XML attachment, mostly packed with gzip or zip. After unpacking you find four parts:
- Who reports and for which period: for example google.com for one day.
- Your published policy: as the recipient read your DMARC record.
- One row per sending server: the server's IP address and how many emails came from it.
- The result per row: whether DKIM and SPF passed, for which domain, and what the recipient did: delivered, put into spam or rejected.
Failure reports with details of each email (the address after ruf=) are hardly sent by any large provider any more. The aggregate reports are enough for everything you need to know.
How to read the reports
- Group by server. What matters is not the single report, but which IP addresses appear over several days and how many emails they send.
- Recognise your own servers. Your mail provider, your web server, your newsletter service, your shop: these servers are meant to send in your name. Their mail should pass.
- For your own servers, find the gap. If SPF never passes, the server is missing from your SPF record. If DKIM never passes, it does not sign with your key.
- Do not mistake forwarding. If an email passes via DKIM but never via SPF, it is often your own mail forwarded by a mailing list or a redirect. That is fine.
- Recognise foreign servers. Servers you do not know whose mail fails are usually trying to misuse your domain. That is exactly what DMARC is meant to stop.
When to tighten the policy
Once all your own servers pass reliably for a few weeks, switch the record from p=none to p=quarantine. Forged emails then land in spam. If all stays quiet, p=reject follows and they are rejected.
A warning sign is a foreign server whose mail passes anyway. Then your SPF record is too broad, for example because of an include of a service that many people use. Check that before you tighten.
Getting the reports under control
By hand this is tedious. Several packed files arrive every day, each full of IP addresses, and the picture only emerges over weeks. It is best to set up a separate mailbox for the reports so that they do not fill your inbox.
That is what the Pro version of Mail Log has a DMARC evaluation for. Mail Log collects the reports from the mailbox, unpacks them, whether gzip, zip or plain XML, and shows you the sending servers with their results. You mark each server as “That's us” or “Foreign”. From this, Mail Log calculates how much of your own sending passes and tells you for each server what is missing: an SPF entry, a DKIM key, or that it is harmless forwarding. A hint shows you when you can tighten the policy.
The Free version checks your DNS records daily and shows the result as a traffic light. The DMARC evaluation is part of the Pro version and included in the membership.
This article is also available in German.

Related extension
A question about this topic, or an idea for the next guide? Write to me.
Norbert Graup
One membership: all Pro versions, updates and personal support.














