Bounce errors / 550 5.7.26 Gmail
How do you fix Gmail error 550 5.7.26 about an unauthenticated sender?
Gmail checked your message and neither SPF nor DKIM passed for your domain. The records in your domain's DNS have to be fixed before Gmail will accept mail from it, and that fix is yours to make.
- Hard bounce
- Who fixes it: You
- Try again: No, fix first
550-5.7.26 This mail has been blocked because the sender is unauthenticated. 550-5.7.26 Gmail requires all senders to authenticate with either SPF or DKIM. 550-5.7.26 Authentication results: 550-5.7.26 DKIM = did not pass 550-5.7.26 SPF [example.com] with ip: [203.0.113.10] = did not pass 550-5.7.26 For instructions on setting up authentication, go to 550 5.7.26 https://support.google.com/mail/answer/81126#authentication - gsmtp
You see this when you send to a Gmail address from a domain whose SPF and DKIM records are missing or wrong.
Here is how to read that message.
Each colour marks one part of the message, and the numbers match the notes underneath.
- 1The reply code550 is a permanent rejection. Gmail will not accept this message until the cause is fixed.
- 2The status code5.7.26 is a Gmail code in the 5.7 family, which covers security and policy. This one is about authentication.
- 3The plain wordsThe sender is unauthenticated: Gmail could not tie the message to the domain it claims to come from.
- 4The resultsThese lines name which checks failed. Start with whichever says did not pass.
Here are other versions of this message you may see.
The words after the code are what separate one cause from another. Find yours.
The version for an SPF hard fail
550-5.7.26 The (E)MAIL FROM domain [example.com] has an SPF record with a 550-5.7.26 hard fail policy (-all) but it fails to pass SPF checks ...
The version for a domain with a DMARC policy
550-5.7.26 Unauthenticated email from example.com is not accepted due to 550-5.7.26 domain's DMARC policy ...
Here is what the message means in plain words.
Gmail wants proof of who sent a message. It looks for two kinds. SPF says the sending server is on the domain's list of allowed servers. DKIM is a digital signature on the message that a receiver can check against a key in the domain's DNS. This error means neither one passed, so Gmail rejected the message before anyone could read it.
Google began enforcing its sender guidelines on 1 February 2024. Every sender needs SPF or DKIM. A sender who sends more than 5,000 messages a day to personal Gmail accounts needs SPF, DKIM and a DMARC record, and the domain in the From address has to line up with the SPF or DKIM domain.
The bounce is about your domain's setup. It is not about the recipient and not about your wording.
These are the usual reasons for it.
- A new domain with no SPF or DKIM records yet.
- The tool that sends your email is not included in your SPF record.
- DKIM is not turned on in the sending tool, or its key was never published in DNS.
- Two SPF records on one domain, or an SPF record that needs more than 10 DNS lookups.
- The From domain does not line up with the domain that passed, so DMARC fails.
- A forwarding step that breaks the original SPF result.
Who has to fix it?
The blue card is the one that fixes it. A dashed card helps in some cases, and a grey card has nothing to do.
550 5.7.26You, the sender
Fixes itYou fix it, or whoever manages your sending domain's DNS does.
The person you emailed
Not involvedNothing to do. The recipient never sees the message.
Their email admin
SometimesOnly for the DMARC version when the From domain belongs to someone else: that domain's admin has to fix it.
Follow these steps to fix it.
- Read the authentication results in the bounce.The lines under Authentication results say which check failed. SPF and DKIM both did not pass in the standard version.
- Run your domain through a health check.The domain health check reads your SPF, DKIM, DMARC and MX records together, so you see what is missing at a glance.
- Fix SPF.Keep one SPF record on the domain and include every service that sends for you. Use the SPF checker to read what you have and the SPF record generator to build a correct one.
- Turn on DKIM and publish the key.Enable signing in your sending tool, then publish the key it gives you in DNS. Google asks for keys of at least 1024 bits and recommends 2048 where your provider supports it. The DKIM checker confirms the key is readable.
- Add a DMARC record.Google says the DMARC policy can start at none. The DMARC record generator builds one in a minute, and the DMARC checker confirms it is live.
- Send yourself a test and read the result.Send a message to a Gmail address, open Show original and look for PASS next to SPF, DKIM and DMARC. The email header analyzer reads the same headers if you paste them in.
- Allow time for DNS.DNS changes can take time to reach every server, up to 72 hours. Test again after that before you send a campaign.
Here is how to stop it from happening again.
Three records decide whether Gmail believes a message. Check them again whenever you add a sending tool or change DNS provider.
DMARC
Ties the checks to your From address and says what to do on a failure.
Open the dmarc record generator →These errors look similar, and here is how they differ.
| Error | Where you see it | What it means | Try again? |
|---|---|---|---|
| 550 5.7.26 | Gmail | This page. The sender is unauthenticated | No, fix first |
| 550 5.7.1 | Gmail | The message looks like unsolicited mail, or the sender's reputation is low. | No |
| 550 5.7.509 | Microsoft 365 | The sending domain fails DMARC and its policy is reject. | No |
| 421 4.7.0 | Gmail | Temporary. One cause is a missing PTR record on the sending IP. | Yes, automatically |
These are the questions people ask about this error.
What is the difference between SPF and DKIM?
SPF checks the sending server against a list the domain published. DKIM checks a signature on the message itself. Gmail asks every sender for at least one of them, and bulk senders for both.
Do I need DMARC to fix 550 5.7.26?
Gmail asks every sender for SPF or DKIM, and senders of more than 5,000 messages a day to personal Gmail accounts for SPF, DKIM and DMARC. Add DMARC either way: it can start at the none policy.
Why does the error happen on some messages and not others?
Authentication can pass from one sending server and fail from another. If one of your sending IPs is missing from SPF and DKIM is not signing, some messages pass and some bounce.
Will email warmup fix it?
No. Warmup builds reputation, and reputation only counts once authentication is right. Fix the records first.
How do I know it is fixed?
Send a test to a Gmail address, open Show original and check that SPF, DKIM and DMARC all say PASS.
Other bounce errors you may run into.
These are the sources behind this page.
The message wording and the fixes come from the providers' own documentation and from the RFC that defines the codes.
Send cold email that passes the checks.
Emailchaser sends your cold emails from your own mailboxes, with warmup and deliverability tools built in.