550-5.7.26 is Gmail permanently refusing a message because it failed authentication. Gmail requires every sender to pass SPF or DKIM, and bulk senders to pass DMARC with alignment, so the fix is always in your DNS records or your mail platform's signing settings, never in the recipient list. Read which variant you got, send a test to find the failing check, fix that record, and retest before resuming.
This page is part of our SMTP error codes guide for cold email. It assumes you send from your own domain through Google Workspace, Microsoft 365 or a hosting provider.
The three variants and what each sentence points to
Gmail's published error list has three 550 5.7.26 messages. On the wire, every line but the last starts 550-5.7.26 and the last starts 550 5.7.26; it is one error spread over several lines.
| Variant (Gmail's wording, abridged) | What failed | Where to look |
|---|---|---|
| "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 [domain] with ip: [IP] = did not pass." | Both SPF and DKIM | SPF record of the envelope domain, and DKIM signing on your server |
| "The (E)MAIL FROM domain [domain] has an SPF record with a hard fail policy (-all) but it fails to pass SPF checks with the ip: [IP]." | SPF hard fail | The SPF record does not list the IP in the bounce |
| "Unauthenticated email from [domain] is not accepted due to domain's DMARC policy." | DMARC under p=quarantine or p=reject | Alignment between From domain and SPF or DKIM domain |
Older bounces, still pasted into forums, use a different opening: "This mail is unauthenticated, which poses a security risk to the sender and Gmail users, and has been blocked. The sender must authenticate with at least one of SPF or DKIM." It means the same as the first variant.
Gmail also has softer relatives. 421 4.7.26 ("rate limited because it is unauthenticated"), 421 4.7.27 (SPF did not pass) and 421 4.7.30 (DKIM did not pass) slow mail down instead of rejecting it, and 451 4.7.26 says DMARC could not be evaluated because of "temporary DNS failures". All of them point at the same records. IANA registers X.7.26 as "Multiple authentication checks failed", which fits the first variant well.
Alignment in one example
Most confusing 5.7.26 bounces are alignment failures, so here is a fictional setup that produces one.
Northfield Consulting sends cold email as anna@northfield-consulting.example through a hosted sending service. A message carries three domains:
| Identifier | Value in this example | Checked by |
|---|---|---|
| From header (what the recipient sees) | northfield-consulting.example | DMARC |
| Envelope sender (MAIL FROM, shown as Return-Path) | bounces.sendingservice.example | SPF |
DKIM signing domain (d= in the signature) | sendingservice.example | DKIM |
SPF passes, because the service's IP is in bounces.sendingservice.example's SPF record. DKIM passes, because the service signs with its own key. But DMARC needs a pass from an identifier "in alignment" with the From domain (RFC 7489 section 4.2). Under relaxed alignment the domains must share the same organisational domain; sendingservice.example and northfield-consulting.example do not. DMARC fails, and if Northfield publishes p=quarantine or p=reject, Gmail returns the DMARC variant of 5.7.26.
The fix is to make at least one identifier match: set up custom DKIM so the service signs with d=northfield-consulting.example, or use a custom return-path subdomain such as bounce.northfield-consulting.example. DKIM is the better choice because it survives forwarding.
Read Authentication-Results in a test message
Before you change DNS, find out what Gmail actually sees.
- From the mailbox that bounced, send a short plain message to a personal Gmail account you control.
- In Gmail, open the message, choose the three-dot menu and Show original.
- The summary at the top lists SPF, DKIM and DMARC as PASS or FAIL. Below it, find the
Authentication-Resultsheader.
A healthy result looks like this (fictional values):
Authentication-Results: mx.google.com;
dkim=pass header.i=@northfield-consulting.example header.s=s1 header.b=Ab12Cd34;
spf=pass (google.com: domain of anna@northfield-consulting.example designates 192.0.2.25 as permitted sender) smtp.mailfrom=anna@northfield-consulting.example;
dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=northfield-consulting.example
What to check:
dkim=must say pass, andheader.iorheader.dshould be your From domain or a subdomain of it. If DKIM shows a different domain, you have the alignment problem above.spf=must say pass, andsmtp.mailfromshows which domain was checked.softfail,failorpermerrorall count as not passing. A permerror is often the 10-lookup limit; see SPF PermError: too many DNS lookups.dmarc=must say pass, andheader.fromis your From domain. If DMARC showspermerror, the record itself is broken; see 554 5.7.5 permanent error evaluating DMARC policy.
If the test passes but campaign mail fails, the campaign is not leaving through the same server. Compare the Received headers of a bounced message with the test.
Fixes per host, with record shapes
Use your own domain in place of northfield-consulting.example. Have one SPF record per domain: RFC 7208 section 4.5 says more than one produces a permerror.
Microsoft 365
- SPF (TXT at the root):
v=spf1 include:spf.protection.outlook.com -allAdd other services that send as your domain with their owninclude:before-all. - DKIM: in the Microsoft Defender portal, open Email authentication settings, then the DKIM tab (
https://security.microsoft.com/authentication), and select your domain. Microsoft shows two CNAME records for theselector1._domainkeyandselector2._domainkeynames. Publish both exactly as shown, wait for Microsoft 365 to detect them, then turn on Sign messages for this domain with DKIM signatures. Until you do, your custom domain has no aligned DKIM signature; only theonmicrosoft.comdomain is signed automatically, and that does not align with your From domain. - DMARC (TXT at
_dmarc):v=DMARC1; p=none; rua=mailto:dmarc-reports@northfield-consulting.example
Google Workspace
- SPF:
v=spf1 include:_spf.google.com ~all - DKIM: in the Admin console, open Gmail's Authenticate email setting, generate a 2048-bit key for the domain, publish the TXT record it gives you (by default at
google._domainkey), wait for DNS, then press Start authentication. Google requires DKIM keys of at least 1024 bits for mail to personal Gmail accounts. Every extra domain or alias domain you send from needs its own key. - DMARC: as above.
cPanel or shared hosting
- SPF: your host's include or IP, for example
v=spf1 +a +mx include:spf.hostingprovider.example ~all. cPanel's Email Deliverability page shows the record it expects and flags problems. - DKIM: cPanel generates a key and shows a TXT record at
default._domainkey. - Watch out: if your DNS is hosted elsewhere (for example at a registrar or CDN), cPanel's records do nothing until you copy them to the real DNS host. That mismatch causes many "but cPanel says it is valid" threads.
Why forwarding and secondary domains trigger it
Forwarding. If your message is forwarded (a recipient's alias, a group, an old domain redirecting to Gmail), the forwarding server's IP sends it on, so SPF fails at Gmail. DKIM survives unless the forwarder changes the message. This is why DKIM aligned to your From domain is the safer foundation: an SPF-only setup will fail on every forwarded message.
Secondary sending domains. Cold senders often add a domain such as northfield-consult.example to protect the main one. Each domain needs its own SPF, DKIM and DMARC. The most common failure is buying the domain, adding mailboxes, and sending before DKIM signing is turned on for it. The cold email deliverability checklist lists every record a new domain needs.
Sending tools. If a tool sends through its own servers rather than through your mailbox's SMTP, it needs its own SPF include and DKIM for your domain. If it relays through your mailbox, your mailbox's records apply.
Retest checklist before resuming a campaign
- Exactly one SPF record exists at the From domain (and at the envelope domain if different).
- The SPF record includes every service that sends as this domain and stays within 10 DNS lookups.
- DKIM signing is enabled for the From domain itself, not the provider's default domain.
- A DMARC record exists at
_dmarcwithv=DMARC1first and a validp=value. - A fresh test to Gmail shows SPF, DKIM and DMARC all PASS in Show original.
-
header.from, the DKIMd=domain and ideallysmtp.mailfromshare the same organisational domain. - The test went through the same server and route the campaign uses.
- Bounced addresses have been kept, not marked invalid.
- The campaign resumes at a lower hourly rate than before.
If the domain has just failed authentication at volume, expect some 421 4.7.28 or 421 4.7.0 deferrals while reputation recovers. See 421 4.7.0 try again later for how to pace that period.
How Map Extract helps
Map Extract's bulk email sender sends through your own SMTP routes, so it cannot authenticate a message your domain has not set up. It can limit the damage while you fix it:
- Bounce auto-pause. Replies and bounces are read over IMAP, and a campaign pauses itself when bounces reach the threshold (5% by default). A wave of 5.7.26 rejections stops the campaign instead of burning through the whole list.
- Test the route first. The SMTP routes screen is where you configure and test each sender and inspect the authentication and connection results of your login before any campaign uses it.
- Review bounces before you suppress. Bounces appear under Replies and bounces. Good addresses that bounced only because of your own DNS should not end up on your suppression list, so check it before you resume.
- Controlled restart. Hourly and daily caps and an optional warm-up ramp let you resume slowly after the fix.
Map Extract does not check SPF, DKIM or DMARC for your sending domain and does not change DNS records for you. Set those up with your mail provider and verify them with a test message as described above.
Key takeaways
- 550-5.7.26 is an authentication failure on your side; the recipient addresses are fine.
- The bounce text tells you which variant: SPF and DKIM both failing, SPF hard fail, or DMARC.
- DMARC needs alignment: SPF or DKIM must pass for the same organisational domain as your From address.
- Custom DKIM for your own domain is the most robust fix and survives forwarding.
- Always confirm with Show original on a test message before resuming, then resume slowly.
Frequently asked questions
What does 550-5.7.26 mean in Gmail?
It is a permanent rejection because the message failed Gmail's authentication checks. The text says which: either neither SPF nor DKIM passed, or SPF hard failed under a -all record, or the message failed the sender domain's DMARC policy. Gmail requires every sender to pass SPF or DKIM, and bulk senders to pass DMARC with alignment. Fix the record named in the bounce before sending again.
Why do I get 550-5.7.26 when SPF and DKIM both pass?
Because they pass for the wrong domain. DMARC needs an aligned pass: the SPF-checked envelope domain or the DKIM signing domain must match the domain in your From address. If your email platform signs with its own domain and uses its own bounce domain, both checks pass but DMARC fails. Set up custom DKIM signing for your own domain.
How long does it take to fix a 550 5.7.26 error?
The DNS change itself is quick, but records need time to propagate according to their TTL, often minutes and sometimes a few hours. Publish the corrected SPF, DKIM or DMARC record, wait, then send a test to a Gmail account you control and check that Show original reports SPF, DKIM and DMARC as PASS before resuming the campaign.
Should I resend emails that bounced with 5.7.26?
Yes, but only after the fix is confirmed with a test message. The addresses are not the problem, so do not remove them from your list or mark them as invalid. Resend at a reduced rate, because a burst of retries straight after an authentication failure can trigger Gmail's rate limiting on a domain whose reputation has just taken a knock.
Sources
Written by the Map Extract editorial team. Found an error? Email support@mapextract.uk and we will check and correct it. How we research guides: editorial policy.