1. Home
  2. SMTP codes
  3. 550 5.7.27
Permanent failure — do not retry
BlockAbout your sending, not the address

SMTP 550 5.7.27

SPF authentication failed (Gmail)

SMTP 550 5.7.27 means Gmail blocked the message because it did not pass SPF. The IP that sent it is not authorised in the SPF record of the envelope sender's domain. Add the sending service to your SPF record, or send through a service that is already in it.

Should you remove the address?

Keep the address; fix the sending side

Keep it. SPF is your domain's setup.

Block. Retrying changes nothing until the cause on your side is fixed.

How it appears

550 5.7.27 This message was blocked because it didn't pass SPF authentication.

421 4.7.27 Your email has been rate limited because SPF authentication didn't pass for this message.

What causes it

  • A new sending service was never added to the SPF record.
  • The SPF record has a syntax error, or exceeds the 10-lookup limit and returns a permerror.
  • The domain has more than one SPF record, which makes SPF fail.
  • Mail is being forwarded through a server that is not in your SPF record.

How to fix it

In order — try the first one first.

  1. Look up your SPF record and check that every service that sends for you is included.
  2. Merge multiple SPF records into one and reduce lookups if you are over 10.
  3. Set up DKIM as well, so authentication does not depend on SPF alone.

Who sends it

Gmail.

Common questions

What does SMTP 550 5.7.27 mean?
SMTP 550 5.7.27 means Gmail blocked the message because it did not pass SPF. The IP that sent it is not authorised in the SPF record of the envelope sender's domain. Add the sending service to your SPF record, or send through a service that is already in it.
Should I retry a 550 5.7.27 error?
No. 550 is a permanent failure, so the message will never be delivered no matter how many times you try. Remove the address — repeated sends to permanent failures are one of the main signals mailbox providers use to throttle a sender.
How do I fix SMTP 550 5.7.27?
Look up your SPF record and check that every service that sends for you is included.
Is 550 5.7.27 a hard bounce or a soft bounce?
550 5.7.27 is a block rather than a classic hard or soft bounce. The rejection is about your sending (authentication, reputation, content or the recipient's policy), not about whether the address exists. Retrying changes nothing until the cause on your side is fixed.
Should I remove the address after a 550 5.7.27 bounce?
Keep it. SPF is your domain's setup.
Will verifying my list prevent 550 5.7.27?
Not directly. This code is about your authentication, IP or domain reputation, so verification will not lift it. A clean list still matters, because mailbox providers weigh how often a sender hits addresses that don't exist.

Clean the list before the next send.

A bounce report only tells you about the addresses you already mailed. The rest of the list has the same kinds of dead mailboxes in it, and each one becomes a hard bounce recorded against your domain the moment you send.

  • A real SMTP mailbox check on every row, before anything is sent
  • Dead and mistyped addresses split out, so they never reach your sending tool
  • Catch-all, disposable and role addresses flagged alongside

Plans from $9 a month, cancel anytime, no contract. Sign in with Google and your first 100 email checks are free, no card. The free tools stay free either way.

Other 550 replies

Sources

Provider wording is quoted only where the provider publishes it.

Last reviewed 2026-10-22

Clean your next list before it bounces

100 free email checks when you sign in with Google, no card. Then monthly plans from $9, or one flat price with fair use, never cut off.

100 free checks, no card Cancel anytime Secure payment by Stripe