Opens in a new tab

Gmail 550 5.7.26: unauthenticated email is not accepted due to the domain’s DMARC policy

Gmail rejected the message because it could not confirm it came from the domain in the From address: SPF and DKIM both failed, or failed to align, and the domain’s DMARC policy says to reject such mail.

550 5.7.26 Unauthenticated email from example.com is not accepted due to domain's DMARC policy. Contact the administrator of example.com domain if this was legitimate email. To learn about the DMARC initiative, go to Control unauthenticated email from your domain. - gsmtp
4 other wordings of the same rejection

Neither SPF nor DKIM passed:

550 5.7.26 This email has been blocked because the sender is unauthenticated. Gmail requires all senders to authenticate with either SPF or DKIM. Authentication results: DKIM = did not pass SPF [example.com] with ip: [203.0.113.5] = did not pass. For instructions on setting up authentication, go to Email sender guidelines. - gsmtp

SPF ends in -all and failed:

550 5.7.26 The (E)MAIL FROM domain [example.com] has an SPF record with a hard fail policy (-all) but it fails to pass SPF checks with the ip: [203.0.113.5]. To best protect our users from spam and phishing, the message has been blocked. For more information, go to Email sender guidelines. - gsmtp

Temporary: unauthenticated mail rate limited:

421 4.7.26 This email has been rate limited because it is unauthenticated. Gmail requires all senders to authenticate with either SPF or DKIM. Authentication results: DKIM = did not pass SPF example.com with ip: 203.0.113.5 = did not pass. To resolve this issue, go to Email sender guidelines. - gsmtp

Temporary: DMARC could not be evaluated because of a DNS failure:

451 4.7.26 Unauthenticated email from example.com is not accepted due to domain's DMARC policy, but temporary DNS failures prevent authentication. Please contact the administrator of example.com domain if this was a legitimate email. To learn about the DMARC initiative, go to Control unauthenticated mail from your domain. - gsmtp

Your bounce names your own domain and sending address where this one says example.com and 203.0.113.5.

Code550 5.7.26
Sent byGmail
TypePermanent — not retried
CauseDMARC

Check your domain’s SPF, DKIM and DMARC

Enter the domain in your From address. We read its records the way Gmail does.

What it means

All three wordings are the same failure seen from different sides: nothing that authenticated the message matched the From domain. With a DMARC policy of reject (or quarantine), Gmail follows the domain’s instruction; without one, Gmail’s own rules require every sender to pass SPF or DKIM.

The -all wording means the envelope domain’s SPF record ends in a hard fail and the sending server is not in it.

The 4.7.26 versions are temporary: Gmail is slowing the sender down, or could not look up DNS, and the sending server will retry. If nothing changes they usually become the permanent 5.7.26.

Why it happens

  • A service sending as your domain — a newsletter tool, CRM, helpdesk or invoicing app — is not in your SPF record and does not sign with DKIM for your domain.
  • Mail forwarded through another server: forwarding breaks SPF, and only a DKIM signature for your domain survives it.
  • A DKIM key that was removed, rotated or never published, so signatures fail.
  • Someone else sending as your domain (spoofing) — in which case the rejection is DMARC doing its job.

How to fix it

  1. Check your domain below: it shows whether SPF, DKIM and DMARC are published and valid.
  2. Find which service sent the rejected message — the sending server’s address is in the bounce — and set up DKIM for your domain in that service. Our email setup guides give the exact records for Google Workspace, Microsoft 365, SendGrid, Mailchimp and others.
  3. Add the service to SPF if it sends with your domain as the bounce address, keeping the record under 10 DNS lookups.
  4. Point DMARC reports (rua=) at a mailbox that reads them, so you see every sender failing before you tighten the policy further.

Email setup guides for each sending service →

Read your DMARC reports free →

Questions

We only send from Google Workspace. Why does Gmail reject us?

Usually because DKIM was never switched on for your domain in the Admin console, and the message was forwarded or sent from a second domain, so SPF did not align either. Turn on DKIM (Apps → Google Workspace → Gmail → Authenticate email).

Should I weaken our DMARC policy to stop the bounces?

Only briefly, to p=none, while you fix the failing sender. The rejection is protecting your domain from forgery; the lasting fix is authenticating the sender.

Sources

Message text and meaning checked on 25 September 2026 against these official sources:

Catch it before the bounces start

Add your domain and we monitor what these bounces are about — SPF, DKIM, DMARC, your sending servers on the blocklists, Gmail’s spam rate — every day, and email you the day something changes. Free for your first domain.

Create a free account