Skip to content
DMARC Pulse

Email errors

550 5.7.26: why Gmail blocked your email and how to fix it

550 5.7.26 means Gmail blocked your message because it failed sender authentication. Identify your bounce and fix SPF, DKIM or DMARC alignment.

What this means

550 5.7.26 means the receiving server refused your message permanently because it failed sender authentication. SPF lists the servers allowed to send for a domain, DKIM signs each message, and DMARC checks that one of them passes for a domain matching the visible From: address.

Google documents three messages under this code, and Gmail's errors always include gsmtp.

  • SPF and DKIM both failed: This email has been blocked because the sender is unauthenticated.
  • SPF hard fail: The (E)MAIL FROM domain [domain-name] has an SPF record with a hard fail policy (-all)
  • DMARC rejection: Unauthenticated email from domain-name is not accepted due to domain's DMARC policy.

RFC 7372 registers this code for a message that failed more than one authentication check, but one of Gmail's messages under this code names only an SPF failure. Other receivers can use their own text.

Gmail's 421 4.7.26 (rate limit) and 451 4.7.26 (temporary DNS failure) are temporary, so your server can retry. A 421 needs the same fixes.

Why it happens

  • SPF and DKIM both failed. A server or service sends as your domain without being in your SPF record and without a valid DKIM signature.
  • SPF hard fail. The SPF record of the domain named ends in -all, and the sending IP is not listed. That domain is the envelope sender (MAIL FROM, the return address), which can differ from your visible From: address.
  • DMARC rejection. The From: domain, its organizational domain or its public suffix domain publishes a DMARC policy, and neither SPF nor DKIM passed on a domain aligned with the From: domain (same domain or, in relaxed mode, same organizational domain).

How to fix it

  1. Identify the sender from the bounce. The SPF messages show the sending IP and domain. Google's DMARC message names only the From: domain, so check which service sent it. Do not add an IP you cannot identify, because SPF would authorize it. If a recipient's forwarder caused the failure, leave SPF alone: DKIM can survive forwarding.
  2. Check your records with the Email Security Score. A custom DKIM selector (key name) can show as missing.
  3. Add the sender to SPF on the domain the SPF result names. If that domain is the service's own, or the bounce names none, go to step 5. Merge the value from its documentation into the record, as in v=spf1 ip4:203.0.113.25 include:_spf.google.com ~all. Caution: keep one SPF record per domain, because a second record returns permerror, and stay within 10 DNS lookups. List every sending service first, because omitting one can block its mail.
  4. For the hard fail, add the server first. Google recommends ~all, but changing only the ending leaves the server unauthorized (softfail).
  5. Set up DKIM in each service that sends as your domain: publish its DNS record first, then turn on signing with your domain.
  6. For the DMARC message, align one identifier. If you own the From: domain, sign with it or use a return address on it that SPF authorizes. If you do not, send from your own domain or contact the From: domain's administrator. In a mail app, Google suggests the outgoing server that matches your address. Google says strict alignment makes rejection or spam placement more likely.
  7. Be careful with the DMARC policy. Lowering p=reject to p=none does not make the message pass DMARC, and it removes your request to reject failures. If you use it as a stopgap, restore the earlier policy once your reports (they need a rua= address) show every legitimate source passing.

Confirm the fix

  1. Allow up to 48 hours: Google says SPF and DKIM can take that long.
  2. Send a new message through the same server to a Gmail address other than the sender. Google says a test message to yourself cannot verify DKIM.
  3. Open the message, click More next to Reply, then Show original. Find Authentication-Results and look for spf=pass or dkim=pass, plus dmarc=pass if a DMARC policy applies to the From: domain (its own record or one inherited from its organizational or public suffix domain).
  4. Repeat for every service that sends as your domain. Your DMARC aggregate reports show which sources still fail.

Check it now

DMARC, SPF, DKIM, MX, blocklists and BIMI in one score

Frequently asked questions

Are 550-5.7.26, 5505.7.26 and 550 5.7 26 the same error?
Yes. SMTP servers put a hyphen after the code on every line of a multi-line reply except the last one, which gives 550-5.7.26. The forms 5505.7.26 and 550 5.7 26 are the same code written without a space or a dot.
Does Gmail reject every unauthenticated message?
Google does not say that. Its sender guidelines say unauthenticated messages might be marked as spam or rejected with a 5.7.26 error, so the same problem can appear as spam placement instead of a bounce.
Does this apply if I only send a few emails?
Yes. Google requires SPF or DKIM from all senders to Gmail accounts. The requirement to set up DMARC starts above 5,000 messages per day to Gmail accounts. Google's DMARC message cites the policy of the domain in your From: address, so it can reach a small sender too.
Will the message arrive by itself once I fix the records?
No. A 550 reply is a permanent refusal, and the sending server should not repeat the same request. Send the message again after the fix takes effect.

Sources consulted

RFC 9989 §4.7 (DMARC tags)
checked 2026-11-08
RFC 7208 §2.6.3 (SPF pass)
checked 2026-11-08

Related pages

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.