Email errors
DMARC reports not received: causes and how to fix it
DMARC reports not received? Check the rua tag, the _report._dmarc record for outside addresses, the mailbox and whether the receiver sends reports.
What this means
DMARC reports not received? The causes are few: a wrong or missing rua tag (the reporting address in your DMARC record), an outside address without permission, a mailbox that cannot take the report, too little time, or a receiver that sends none. An aggregate report is an XML summary, usually daily, of the mail a receiving server (the receiver) saw using your domain.
If a lookup finds no record at all, see no DMARC record found. Missing failure reports from the ruf tag are expected. Receivers may skip them, Gmail does not support the tag and Microsoft 365 does not send them.
Why it happens
- No
ruatag. Without it, receivers must not generate aggregate reports. A subdomain with its own DMARC record needs its ownrua. - Two records at one name. Receivers discard them all.
- A malformed address.
ruatakes a URI, sodmarc@example.comwithoutmailto:is malformed and receivers should ignore it. - An outside address without permission. An address outside your Organizational Domain (usually the domain you registered) needs a permission record at the destination. Without one, receivers must ignore it.
- A mailbox that cannot take them. If delivery fails, the receiver may retry later or discard the report. A report can also exceed an attachment size limit.
- Too little time or traffic. A report typically covers one UTC day and needs at least one
recordelement, so a receiver that saw none of your mail sends nothing. - The receiver does not report. RFC 9989 does not oblige receivers to send reports. Microsoft 365 sends none when the recipient's mail reaches another service first.
How to fix it
-
Read your record on a public DNS server. For a subdomain with no record of its own, query its Organizational Domain (usually the domain you registered). Its reports arrive under that domain's name.
nslookup -type=TXT _dmarc.example.com 1.1.1.1If two answers begin with
v=DMARC1, merge them into one record and delete the other. Ifruais missing or lacksmailto:, correct it in that record:TXTv=DMARC1; p=none; rua=mailto:dmarc@example.com
Caution: edit the existing record, because a second one makes receivers discard both.
p=noneis only a sample. If the record works today, change onlyruaand keeppand every other tag, such asspandt, exactly as they are. Repairing a broken or duplicated record withquarantineorrejectinporspenforces that policy as soon as receivers read it. In that case, publishp=nonefirst withoutspand tighten it after reviewing reports. -
An address under the same registered domain as the record, such as
dmarc@reports.example.com, needs no permission, so go to step 4. -
For an outside address, query the permission record. Its name is the domain that publishes your DMARC record, then
_report._dmarc, then the full host after@. Forrua=mailto:dmarc@reports.example.netonexample.com:nslookup -type=TXT example.com._report._dmarc.reports.example.net 1.1.1.1You want a TXT answer (a text entry in DNS) that begins with
v=DMARC1. If none appears, the destination's owner must publish it, so ask your reporting service. If you run that domain, add this value at that name and check the saved name, because some DNS hosts add the zone automatically:TXTv=DMARC1; -
Send a normal message to the
ruaaddress from an outside account. If it bounces or vanishes, fix the mailbox or its routing first. A reporting service's address can discard ordinary mail, so ask the service instead. Then search the mailbox and spam folder forReport Domain:, which begins the subject line, and check that filters let compressed attachments through. -
Send mail and wait at least one full UTC day.
Confirm the fix
-
Repeat the queries, or run the DMARC checker on the domain that publishes the record. It flags a missing
rua, a malformed address, two records at one name and an outside address with no permission record. -
If a new permission record does not show up, DNS servers may hold the earlier empty answer until its cache time runs out. Query again later.
-
Look for the first report.
-
Silence from everyone after several days of steady mail to many outside recipients points back to your record or mailbox.