Skip to content
SIA "OATS"
All writing Security

DMARC Check Failed: What It Means and How to Fix It

16 November 2026 · 4 min read

Gmail can reject unauthenticated mail with a 5.7.26 error.1 When that code turns up in a bounce from your own invoice run, the message failed the receiver’s authentication check. Nobody forged it. The mail that got stopped was yours.

What the check tests

DMARC asks one question. Did SPF or DKIM pass for a domain that matches the one in the From line?2 SPF lists the servers allowed to send for your domain. DKIM signs each message with a key published in your DNS. Either one can carry the pass, but only if its domain lines up with the address your reader sees.

That last part trips people up. A newsletter tool can send your campaign through its own servers, pass SPF for its own domain, and still fail DMARC for yours. The check passed for the wrong name.

Alignment comes in two strengths. Relaxed means the same organisational domain, so mail.example.lv counts for example.lv. Strict means the exact same domain. Relaxed is the default for both SPF and DKIM.2

Why your own mail fails

Start with the services that send in your name. The newsletter tool, the invoicing software, the CRM, the contact form on your site. Each one needs either a DKIM key for your domain or a place in your SPF record. Miss one and that stream fails.

SPF has a hard ceiling. A receiver stops after 10 DNS lookups and returns an error,3 so a record that includes six or seven services can break without anyone touching it.

Forwarding is the other classic. When a client forwards your message on, SPF fails, because the forwarder isn’t one of your servers. Mailing lists that add a footer or a subject tag break the DKIM signature too.4 You can’t fix those from your side. What you can do is make sure each message carries both, so one failing doesn’t sink it.

Who enforces it now

Since February 2024, Google has required anyone sending 5,000 or more messages a day to Gmail to publish DMARC, with aligned SPF or DKIM.1 Yahoo set the same rule for its bulk senders that month.5 Microsoft followed for Outlook.com, Hotmail and Live. After 5 May 2025 it began routing mail from non‑compliant high‑volume domains to Junk, and it says rejection comes later, on a date still to be announced.6

Under 5,000 a day, Gmail still wants SPF or DKIM on every message. DMARC isn’t required for you yet. But a receiver that finds your DMARC record acts on it whatever your volume.

Fix it in this order

  1. Add a report address. The rua= tag tells receivers where to send summaries of who sent mail in your name and whether it passed. Without it you’re guessing.
  2. Read a week of reports and list every service that sends for you. Turn on DKIM with your own domain in each one, and keep SPF under 10 lookups.
  3. Stay on p=none while you do this. Google’s own rollout advice is about a week there, then quarantine once your mail runs clean.7
  4. Move to p=quarantine, then p=reject when the reports show nothing of yours failing.

This is the record on oats.lv today:

v=DMARC1; p=quarantine; rua=mailto:info@oats.lv; fo=1; adkim=r; aspf=r

Forged mail goes to spam, reports come to me, alignment is relaxed.

What changed in 2026

DMARC moved onto the IETF standards track in May 2026 as RFC 9989.2 The version tag is still v=DMARC1, so you don’t need to rewrite a record that works. One tag is gone. pct, the percentage dial for a gradual rollout, was dropped because receivers only applied it reliably at 0 or 100. Its replacement is t=y, which asks receivers to apply your policy one step softer while you test.

Where the free scan fits

The scan at oats.lv/scan reads your DMARC, SPF and DKIM records and flags a missing record, a policy stuck on p=none, or no report address. For DKIM it tries the 20 most common key names, so a service with an unusual one can slip past it. The email security fix is listed at 79 EUR, and the final price is confirmed by email before any work starts.

If your own mail is failing, look for the service you forgot and the record nobody has opened since the domain was bought. The bounce with 5.7.26 in it is that record, finally getting read.

Sources and notes


  1. Google, Email sender guidelines. https://support.google.com/a/answer/81126 ↩↩

  2. RFC 9989, Domain‑Based Message Authentication, Reporting, and Conformance (DMARC), May 2026, sections 3.2.10, 4.1, 4.7 and appendix A.6. https://www.rfc‑editor.org/rfc/rfc9989.html ↩↩↩

  3. RFC 7208, Sender Policy Framework, section 4.6.4. https://www.rfc‑editor.org/rfc/rfc7208#section‑4.6.4 ↩

  4. RFC 7960, Interoperability Issues between DMARC and Indirect Email Flows, September 2016, sections 2.2 and 2.3. https://www.rfc‑editor.org/rfc/rfc7960.html ↩

  5. Yahoo, Sender Best Practices. https://senders.yahooinc.com/best‑practices/ ↩

  6. Microsoft, Outlook’s new requirements for high‑volume senders, 2 April 2025, updated 30 April 2025. https://techcommunity.microsoft.com/blog/microsoft‑defender‑for‑office‑365‑blog/strengthening‑email‑ecosystem‑outlook%E2%80%99s‑new‑requirements‑for‑high%E2%80%90volume‑senders/4399730 ↩

  7. Google Workspace, Recommended DMARC rollout. https://knowledge.workspace.google.com/admin/security/recommended‑dmarc‑rollout ↩

Scan your site

Find out what attackers and AI assistants see on your page. Enter the address and get a report.

Write to me

or write directly: