Opens in a new tab

Gmail 550 5.7.27: the message didn’t pass SPF authentication

Gmail requires bulk senders — more than 5,000 messages a day to Gmail — to pass SPF, and this message did not: the server that sent it is not authorised by the SPF record of the envelope (bounce) domain.

550 5.7.27 This message was blocked because it didn't pass SPF authentication. Gmail requires bulk email senders to authenticate their email with SPF. Authentication results: SPF with 203.0.113.5 = did not pass To set up SPF for your sending domains, visit Set up SPF. To learn more about Gmail requirements for bulk email senders, visit Email sender guidelines. - gsmtp
1 other wording of the same rejection

Temporary:

421 4.7.27 Your email has been rate limited because SPF authentication didn't pass for this message. Gmail requires all bulk email senders to authenticate their email with SPF. Authentication results: SPF domain-name with IP address: 203.0.113.5 = Did not pass. To set up SPF for your sending domains, visit Set up SPF. To learn more about Gmail requirements for bulk email senders, visit Email sender guidelines. - gsmtp

Your bounce names your own domain and sending address where this one says example.com and 203.0.113.5.

Code550 5.7.27
Sent byGmail
TypePermanent — not retried
CauseSPF

Check your domain’s SPF, DKIM and DMARC

Enter the domain in your From address. We read its records the way Gmail does.

What it means

SPF is checked against the domain in the envelope sender (the Return-Path), not necessarily the one in the From address. The address in the bounce is the server Gmail saw; it is not listed in that domain’s SPF record, or the record could not be evaluated.

The 421 4.7.27 version is temporary: Gmail is slowing delivery and the sending server will retry.

Why it happens

  • A new sending service, or a new server, that was never added to SPF.
  • An SPF record over 10 DNS lookups, which makes the whole record fail.
  • Two SPF records on the domain, which receivers treat as a permanent error.
  • Mail relayed or forwarded through a server that is not yours.

How to fix it

  1. Check your SPF record below — it shows the lookups used, and any error that makes it fail for every server.
  2. Add the missing service’s include (or the server’s address) to the one SPF record you have.
  3. If the record is at or over 10 lookups, remove includes you no longer use, or flatten it with hosted SPF.

Follow every include in your SPF record →

Build a correct SPF record →

Questions

SPF passes in my test. Why does Gmail say it failed?

Check the address in the bounce: Gmail judges the server that actually connected. A test from your own mail app often goes through a different server than a newsletter tool or a forwarding rule.

Sources

Message text and meaning checked on 25 September 2026 against these official sources:

Catch it before the bounces start

Add your domain and we monitor what these bounces are about — SPF, DKIM, DMARC, your sending servers on the blocklists, Gmail’s spam rate — every day, and email you the day something changes. Free for your first domain.

Create a free account