Inbox check guide
Gmail 550 5.7.26 “sender is unauthenticated”: what it means and the exact fix
Reviewed
Short answer
550 5.7.26 means Gmail couldn’t confirm the message really came from your domain. Every sender to Gmail must pass SPF or DKIM; if the domain publishes DMARC, one of them must also align with the From: address. Read the full bounce text: it says whether SPF hard-failed, DMARC refused the message, or nothing authenticated at all. Fix that one record and the bounces stop.
Check your domain now
The three versions of the message
Gmail uses the same code for three different failures. The words after 5.7.26 tell you which one you hit, so copy them from the bounce before you change anything:
| The bounce says | What failed | What to fix |
|---|---|---|
| “This email has been blocked because the sender is unauthenticated.” | Neither SPF nor DKIM passed for the sending domain. | Add the sending service to SPF, and turn on DKIM signing for your domain in that service. |
| “The (E)MAIL FROM domain … has an SPF record with a hard fail policy (-all) but it fails to pass SPF checks” | The server that sent the message isn’t in your SPF record, and the record ends in -all. | Add the missing service’s include to your one SPF record. |
| “Unauthenticated email from … is not accepted due to domain’s DMARC policy” | Your DMARC policy is quarantine or reject, and neither SPF nor DKIM passed for the From: domain (aligned). | Make the service sign with DKIM as your domain; don’t weaken DMARC unless you must. |
Find the failing check in the message headers
If a copy of the message reached any Gmail inbox (a test account works), open it, choose Show original and read the SPF, DKIM and DMARC lines at the top. In the raw headers, the Authentication-Results line shows the same verdicts with the domains that were checked.
Look at which domain each check used. spf=pass for the newsletter tool’s own bounce domain and dkim=pass for d=sendgrid.net both “pass”, but neither is your domain, so DMARC still fails. Alignment means the domain in SPF or DKIM matches the domain people see in From:.
Authentication-Results: mx.google.com;
dkim=pass header.i=@sendgrid.net;
spf=pass smtp.mailfrom=bounces.sendgrid.net;
dmarc=fail (p=QUARANTINE) header.from=yourdomain.comThe fix, step by step
- List every service that sends as your domain: your mailbox provider, newsletter tool, shop, invoicing, CRM, website forms.
- Make sure your domain has exactly one SPF record, and that it includes each of those services. Two SPF records count as no record.
- In each service, turn on domain authentication (often called “authenticate your domain” or “custom DKIM”) and publish the DKIM records it gives you. DKIM survives forwarding; SPF doesn’t.
- If you have no DMARC record yet, add one with p=none so reports tell you what else sends as you.
- Send a test to a Gmail address and check Show original: SPF or DKIM should pass for your own domain, and DMARC should say PASS.
v=spf1 include:_spf.google.com include:servers.mcsv.net ~allv=DMARC1; p=none; rua=mailto:dmarc@yourdomain.comWhen it’s forwarding, not you
A message you sent correctly can still bounce with 5.7.26 if someone forwards it automatically to Gmail: the forwarding server isn’t in your SPF record. DKIM normally survives forwarding, so signing with DKIM for your own domain is the durable fix. If the forwarder changes the message (a mailing list adding a footer), DKIM breaks too, and the list itself needs to use ARC or rewrite the From: address.
Questions
Is 550 5.7.26 a temporary error?
No. Codes starting with 5 are permanent refusals: the message won’t be retried and the recipient never sees it. The temporary relative is 421 4.7.26, which Gmail uses to rate-limit unauthenticated mail before it starts refusing it.
Will changing DMARC to p=none fix 5.7.26?
It can stop one version of the bounce, but it removes your protection against forged mail and doesn’t fix the cause. Gmail still requires SPF or DKIM to pass, and unauthenticated mail still goes to spam. Fix authentication for the service that sends instead.
Why do only some of my emails bounce with 5.7.26?
Usually because only one sending service is misconfigured: your mailbox passes, but the invoicing tool or website form sends from a server not in SPF and without DKIM. Check the headers of a bounced message to see which server sent it.
Do I need to send 5,000 emails a day for this to apply?
No. SPF or DKIM is required of every sender to Gmail. The 5,000-a-day threshold adds DMARC, alignment, one-click unsubscribe and a spam-rate limit on top.