The domain in the From address has no DMARC record, so there is no policy to apply and no reports come back. Gmail, Yahoo and Microsoft now require bulk senders to publish one — even p=none is enough to meet the rule and start seeing who sends as the domain.
dmarc=none action=none header.from=example.com
How other mail servers write it
Yahoo and AOL
dmarc=none header.from=example.com
| Result | dmarc=none |
| Usually fixed by | The sending domain’s owner |
| Looked up at | _dmarc.example.com, then each parent domain (RFC 9989’s DNS tree walk) |
| Gmail | Writes no dmarc= at all when there is no record |
| Gmail rejects | Bulk mail without DMARC: 5.7.40 |
Check the DMARC record
Enter the domain from header.from: we find its DMARC record, walking up from a subdomain, and explain every tag.
What it means
Receivers look for a DMARC record at _dmarc under the From domain, and — under RFC 9989 — at each parent domain in turn. Finding none, DMARC simply does not apply. For bulk senders that is now a failure in itself: Gmail and Yahoo require a DMARC record, as Microsoft does for 5,000 or more messages a day to Outlook.com.
Why it happens
- No DMARC record was ever published.
- The record is under the wrong name — not _dmarc.
How to fix it
- Publish a TXT record at _dmarc with v=DMARC1; p=none; and an rua= address for reports.
- Read the reports, make sure every sender passes, then move to quarantine and reject.
See it for yourself
dig TXT _dmarc.example.com +short
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- RFC 9989: Domain-Based Message Authentication, Reporting, and Conformance (DMARC) — rfc-editor.org
- Anti-spam message headers — learn.microsoft.com
- Email sender guidelines — support.google.com
- Sender Best Practices — senders.yahooinc.com
- Gmail SMTP errors and codes — knowledge.workspace.google.com