550 5.7.26 Unauthenticated Email: What It Means and Fixes
What the Gmail 550 5.7.26 unauthenticated email bounce means, how to tell its three versions apart, and how to fix SPF, DKIM and DMARC so your mail gets through.

You send an email to a Gmail or Google Workspace address, and it bounces with "550 5.7.26". The rest of the message talks about authentication, SPF, DKIM or DMARC. Unlike most bounces, this one is not about the recipient. It is about your own domain setup.
This guide explains what the error means, how to tell its three versions apart, and how to fix each one. Most fixes take a few DNS changes and a short wait.
What 550 5.7.26 means#
The bounce has two parts. 550 is the SMTP reply code for a permanent failure. The server refused the message and will not accept it on a retry. 5.7.26 is the enhanced status code. The 5.7 class covers security and policy problems. At Google, 5.7.26 means the message failed authentication checks.
Google's mail servers check every message for proof that it really comes from the domain in the From address. They use three standards:
- SPF lists the servers allowed to send mail for your domain.
- DKIM adds a signature that proves the message was not changed and was signed by your domain.
- DMARC tells receivers what to do when SPF and DKIM do not line up with the From domain.
When a message fails these checks in a certain way, Gmail rejects it with 550 5.7.26. Google's Gmail SMTP error reference lists the exact wording for each case.
The three versions of the error#
The text after the code tells you which check failed. Read it before you change anything.
1. "The sender is unauthenticated"#
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.
Here, the message passed neither SPF nor DKIM. Gmail needs at least one of them for every sender. This is the most common version for new domains and for tools that send on your behalf without setup.
2. "SPF record with a hard fail policy"#
550 5.7.26 The (E)MAIL FROM domain has an SPF record with a hard fail policy (-all) but it fails to pass SPF checks with the ip.
Your SPF record ends in -all, which tells receivers to reject mail from servers that are not listed. The server that sent this message is not on the list. So Gmail did what your record asked.
3. "Not accepted due to domain's DMARC policy"#
550 5.7.26 Unauthenticated email from example.com is not accepted due to domain's DMARC policy.
The domain in the From address has a DMARC policy of reject. The message did not pass SPF or DKIM in a way that matches that domain. So Gmail followed the policy and refused it.
Pay attention to which domain is named. If it is your domain, the fix is in your DNS. If it is someone else's domain, you are sending mail "from" an address you do not control. More on that below.
How to fix 550 5.7.26 step by step#
Work through these steps in order. Each one rules out a cause.
Step 1: Read the headers of a test message#
Send a test email to a Gmail account you own. Open it, then choose "Show original". Google shows the SPF, DKIM and DMARC results at the top. Our guide on how to read email headers explains each line. This tells you which check fails before you touch DNS.
Step 2: Add every sending service to SPF#
List every tool that sends mail with your domain in the From address. Think about your mailbox provider, your cold email tool, your CRM, your help desk and your billing system. Each needs to be in your SPF record, usually with an include: entry from its docs.
Then check the record with an SPF checker. Keep one SPF record per domain, not two. And stay within the limit of 10 DNS lookups, which our post on the SPF lookup limit explains.
Step 3: Turn on DKIM for each service#
SPF alone breaks when mail is forwarded. DKIM survives it. Turn on DKIM in each sending tool and publish the DNS record it gives you. In Google Workspace, you do this in the Admin console under Gmail authentication. Then send a new test and confirm that DKIM shows "PASS".
Step 4: Make sure the domains align#
DMARC does not only ask whether SPF or DKIM passed. It asks whether they passed for the same domain as the From address. A tool that signs with its own domain passes DKIM but fails DMARC alignment. Use a custom DKIM domain or a custom return-path in each tool, so the signature matches your domain.
Step 5: Review your DMARC policy#
If you just moved to p=reject, some legitimate mail may now bounce. Step back to p=none while you find every sender, then tighten it again. Our guide to DMARC policy none, quarantine and reject shows how to move through each stage safely.
Step 6: Wait, then test again#
DNS changes can take up to a few hours to spread. Send a new test only after the records are live. Do not resend the bounced campaign until the test passes.
When the DMARC error names someone else's domain#
Sometimes the bounce names a domain you do not own. This happens when your system sends mail with another person's address in the From field. Common examples:
- A website contact form that sends the visitor's message "from" the visitor's address.
- A CRM that sends as a rep's personal address.
- A forwarding rule that keeps the original sender's From address.
If that domain has a DMARC reject policy, Gmail refuses the message, and you cannot fix their DNS. The answer is to send from your own domain. Put the other person's address in the Reply-To header instead. Your message stays authenticated, and replies still reach the right person.
How this error affects cold email#
Since 2024, Google has required every sender to use SPF or DKIM. Bulk senders need SPF, DKIM and DMARC. You can read the full rules in Google's email sender guidelines.
For cold email, the safest setup is:
- A separate sending domain or subdomain for outreach.
- SPF, DKIM and DMARC on that domain before the first send.
- A warmup period with low volume.
- A clean list, so bounces do not pile on top of other signals.
Authentication proves who you are. It does not prove that your list is good. A domain with perfect SPF and DKIM can still lose its reputation if many addresses bounce. That is why you should verify emails before each campaign as well.
550 5.7.26 vs similar Gmail errors#
| Code | What it says | Main fix |
|---|---|---|
| 550 5.7.26 | Failed SPF/DKIM, SPF hard fail, or DMARC reject | Fix SPF, DKIM and alignment |
| 550 5.7.27 | Bulk sender failed SPF | Add the sending IP to SPF |
| 550 5.7.1 | Blocked by policy or reputation | Improve reputation and content |
| 550 5.1.1 | Mailbox does not exist | Remove or correct the address |
Our list of email bounce codes covers the rest.
A quick checklist#
- Read the full bounce text and note which version you have
- Check SPF, DKIM and DMARC results in a test message
- Add every sending tool to one SPF record
- Turn on DKIM in each tool
- Align the DKIM and return-path domains with your From domain
- Relax DMARC to
p=nonewhile you fix senders, then tighten it - Send from your own domain, never "as" someone else's
- Test again before you resend
FAQ#
What does 550 5.7.26 mean in Gmail?#
It means Gmail rejected your message because it failed authentication. Either SPF and DKIM both failed, your SPF hard fail rule blocked the sending server, or the From domain's DMARC policy told Gmail to reject it.
Is this a hard bounce?#
Yes. It is a permanent failure, but it is not about the recipient. Fix your domain's authentication, then send again. Do not remove the contact from your list for this reason alone.
How long does it take to fix this error?#
The DNS changes take minutes to make. Spreading them can take up to a few hours. Most senders can fix it the same day.
Can I fix the error if it names another company's domain?#
Not on their side. Stop sending with their address in the From field. Send from your own domain and use Reply-To for their address.
Do I need DMARC to avoid this bounce?#
Every sender needs SPF or DKIM. Bulk senders to Gmail also need a DMARC record. Setting up all three is the simplest way to stay safe.
Fixed your authentication? Make sure your list is just as clean: check it with the Tomba Email Verifier before your next send.
// start free
See who Tomba finds at any company
Type a company's domain to see its people, their roles and verified work emails, each with the pages it was found on. Free account, no card.
Free plan · No credit card required · GDPR & CCPA
// about the author