If emails to Gmail addresses are bouncing back with a 550 5.7.26 error, Google has rejected them before they reached the inbox or the spam folder. Since November 2025, Google has been permanently rejecting more non-compliant bulk mail rather than just slowing it down, so this error has become far more common.
The good news: 5.7.26 is almost always an authentication problem, and authentication problems are fixable.
What the error says
The bounce usually contains one of two messages:
550 5.7.26 This mail has been blocked because the sender is unauthenticated.
Gmail requires all senders to authenticate with either SPF or DKIM.
This means neither SPF nor DKIM passed for your email.
550 5.7.26 Unauthenticated email from yourdomain.co.uk is not accepted due to domain's DMARC policy.
This means your domain has a DMARC policy of quarantine or reject, and this email failed DMARC, so Gmail is enforcing your own policy.
Why it’s happening now
Google introduced its sender requirements in February 2024. All senders need SPF or DKIM, and bulk senders (around 5,000 or more emails a day to Gmail) need SPF, DKIM, DMARC, alignment, one-click unsubscribe and a spam complaint rate below 0.3%. Enforcement started gently with temporary errors, then tightened. From November 2025, Google moved to permanently rejecting more mail that doesn’t comply.
How to fix it
1. Find out which email is failing
Look at the bounce: which address sent it, and from which system? It’s often not your main mailbox but something else sending as your domain: a CRM, an invoicing tool, a website contact form or an old marketing platform.
2. Check SPF for that sender
Make sure the service is covered by your SPF record, that you have only one SPF record, and that it stays within the 10-lookup limit. A broken SPF record fails for everything.
3. Set up DKIM signed with your domain
In the sending platform’s settings, find “domain authentication” or “DKIM”, add the records it gives you to your DNS, then verify. The signature should read d=yourdomain.co.uk. Our guide to why DKIM fails covers the usual problems.
4. Check DMARC alignment
For the DMARC version of the error, SPF or DKIM must not only pass but align: the domain they pass for must match the domain in your From address. A platform that passes SPF for its own bounce domain and signs DKIM with its own domain will fail DMARC even though both checks “pass”.
5. Don’t fix it by weakening DMARC
Dropping your DMARC policy back to p=none makes the bounces stop, but it also removes your protection against spoofing. Fix the sender instead. If you need breathing room while you do, read our guide to DMARC policies before changing anything.
Other things that can trigger 5.7.x rejections
If authentication is passing and you’re still being rejected, check that you send over TLS, that your sending IP has valid forward and reverse DNS, that marketing email has one-click unsubscribe, and that your spam rate in Google Postmaster Tools is below 0.3%.
Confirm the fix
Send a new test to a Gmail address, open it, choose Show original, and check that SPF, DKIM and DMARC all show PASS. Then keep an eye on your DMARC reports for any other service failing in the same way.
Stop the Gmail bounces
Send a test email to The Inbox Wizard Test and it shows whether SPF, DKIM and DMARC pass, with a score out of 100. If the bounces are coming from a platform you can’t pin down, we’ll find it and fix it.
