Email authentication guides
One problem per page: what it means, how to check it and how to fix it. Sources at the bottom of each guide.
-
550 5.7.26 and 5.7.515: why Gmail and Outlook reject your mail
Why Gmail answers 550 5.7.26 and Outlook.com 550 5.7.515, the four usual causes (no SPF or DKIM, no alignment, forwarding, missing DMARC) and how to fix each.
Updated
-
Gmail, Yahoo and Microsoft sender requirements (2026)
What Gmail, Yahoo and Outlook.com require of senders in 2026: SPF, DKIM, DMARC, alignment, one-click unsubscribe and spam rate, checked against their own pages.
Updated
-
How to read DMARC aggregate (rua) reports
The fields in a DMARC aggregate (rua) report explained, the difference between policy_evaluated and auth_results, and why forwarding and unknown senders show up.
Updated
-
Moving DMARC from p=none to p=reject safely
A step-by-step DMARC rollout from p=none to quarantine and reject, with what to look for in your aggregate reports before each step.
Updated
-
TLS-RPT reports explained
What SMTP TLS reports (TLS-RPT, RFC 8460) are, how to publish the _smtp._tls record, how to read a report and what each failure type means.
Updated
-
Email authentication checklist when adding a new sending service
What to change in SPF, DKIM and DMARC when a CRM, helpdesk or newsletter tool starts sending as your domain, and how to check that nothing else broke.
Updated
-
Why DMARC reports show sources you don’t recognise
How to tell forwarding, mailing lists, spoofing and your own forgotten services apart in DMARC aggregate reports, from the SPF and DKIM results of each source.
Updated
-
DNS changes that silently break email
Four DNS changes that break mail without an error: a new SPF include over the lookup limit, deleted DKIM records, an expired MTA-STS certificate and a changed MX.
Updated
-
Why you get DMARC reports every day, and where rua should point
Why DMARC aggregate reports arrive every day, who sends them, and where rua should point: your own mailbox, a dedicated one or a service, and the check for other domains.
Updated
-
SPF fail in a DMARC report when the header says pass
Why a DMARC report shows SPF fail when the message header says spf=pass: the SPF result versus SPF alignment in the report, and what forwarding does to both.
Updated