In short: Gmail checked your message for SPF and DKIM, and neither passed for your domain. The fix is to find which server or service sent the message, then authorise it with SPF and turn on DKIM for it. Most cases are fixed with one or two DNS changes.
What the error means
Since 2024, Gmail requires every sender, at any volume, to pass at least one of SPF or DKIM. When neither passes, Gmail refuses the message and your mail server sends you a bounce containing code 550-5.7.26. The wording varies. You may see any of these:
- "This mail has been blocked because the sender is unauthenticated."
- "Gmail requires all senders to authenticate with either SPF or DKIM."
- "This mail is unauthenticated, which poses a security risk to the sender and Gmail users, and has been blocked."
All three mean the same thing. Gmail isn't saying your email looks like spam. It's saying it can't confirm the email came from you.
Read the bounce first
Open the bounce message and look for lines like these:
550-5.7.26 Authentication results:
550-5.7.26 DKIM = did not pass
550-5.7.26 SPF [yourshop.lk] with ip: [203.0.113.25] = did not pass
The IP address is the important part. It tells you which server actually sent the message. Search for that IP, or compare it with your hosting server's IP, to work out whether the message came from your web host, your email provider, or a third-party tool such as a billing system.
Common causes
- A tool sending as you. Billing software, a booking system, a CRM or your website sends email with your address in the From field, but isn't listed in your SPF record and doesn't sign with DKIM.
- No DKIM at all. DKIM was never turned on in your email provider.
- A broken SPF record. Two SPF records, a typo, or more than 10 lookups make SPF fail for every message.
- A recent move. You moved email or hosting, and the old SPF record still points at the old server.
How to fix it
- Identify the sender from the IP address in the bounce.
- Add it to SPF. Edit your existing SPF record. Don't add a second one. Most services give you an
include:value to add, such asinclude:_spf.google.com. - Turn on DKIM in that service. It gives you a record to publish in DNS, then you click verify or activate.
- Add a DMARC record if you don't have one, starting with
v=DMARC1; p=none; rua=mailto:[email protected]. - Wait, then test. DNS changes usually take minutes to a few hours. Send a new message to a Gmail address, open it, choose Show original, and check for SPF PASS or DKIM PASS.
Run the free domain checker after each change to confirm the records are live.
If it only happens sometimes
If some emails get through and others bounce, you probably have more than one sending server and only some of them are authorised. Large providers send from many IP addresses. Make sure your SPF uses the provider's include: value rather than single IP addresses, and that DKIM is turned on, because DKIM doesn't depend on which server sent the message.
Questions
Will Gmail accept my email again straight after I fix it?
Yes. The check happens on every message, so once SPF or DKIM passes, new messages are accepted. Bounced messages aren't retried, so send them again.
Do I need DMARC to fix 550-5.7.26?
Not for this error. It only needs SPF or DKIM to pass. Bulk senders also need DMARC, and every business should have it to stop spoofing.
Still bouncing?
Forward me the full bounce message and I'll tell you exactly what's wrong and what it costs to fix. Most fixes are the Authentication setup package.
Send me the bounce