Skip to main content

Gmail 550 5.7.1: This Message Is Likely Unsolicited Mail

By Tom Sather•Updated October 11, 2026•7 min read

Gmail's 550 5.7.1 'likely unsolicited mail' bounce is a reputation block, not a blocklist. Find the cause in complaints, targeting or links, then rebuild.

On this page

Gmail's 550 5.7.1 "likely unsolicited mail" bounce means Gmail's own filters judged the message to be spam and refused it instead of delivering it to the spam folder. It's a reputation block based on your sending history, recipient complaints and the content or links in the message. No public blocklist is involved, there's no delisting form, and the fix is to change what you're sending and to whom.

It's the most serious reputation signal Gmail gives a sender. Messages that are merely suspicious go to spam. Messages that get 5.7.1 didn't make it that far.

What the bounce says

Google's documented wording:

550-5.7.1 This message is likely unsolicited email. To reduce the amount of
550-5.7.1 spam sent to Gmail, this message has been blocked. For more
550 5.7.1 information, go to https://support.google.com/mail/?p=UnsolicitedMessageError

You'll also see this older version in a lot of real logs, often with the sending IP:

550-5.7.1 [203.0.113.7] Our system has detected that this message is
550-5.7.1 likely unsolicited mail. To reduce the amount of spam sent
550-5.7.1 to Gmail, this message has been blocked.

Make sure you're looking at the right 5.7.1. Gmail uses the same code for unrelated problems: "This email has been rate limited," a message that "does not meet IPv6 sending guidelines regarding PTR records and authentication," and IPs on a suspended list. Those have different fixes. This page covers the "likely unsolicited" one.

What it means

Google's help page says it plainly: if Gmail thinks an email might be spam, it may block it. The factors it lists are spam-like content, the sender's history of sending spam, and, for forwarded mail, the reputation of the forwarding domain.

In practice that history is reputation tied to your sending domain, your DKIM domain, your IPs and the domains linked in your messages. Google's sender guidelines make clear that recipient feedback, especially spam reports, and whether people asked for your mail weigh heavily in it. Once that reputation is bad enough, Gmail stops filtering your mail to spam and starts refusing it.

That's why 5.7.1 often follows a stretch of rising spam placement and 421 4.7.28 deferrals.

Common causes, most likely first

  1. Mailing people who didn't ask for it. Purchased or rented lists, scraped addresses, co-registration, pre-checked boxes, or a "we'll add everyone from the trade show" import. Google lists all of these under sending practices to avoid.
  2. A high spam rate. Your user-reported spam rate in Postmaster Tools has been above 0.1% for a while, or has reached 0.3%.
  3. Old, unengaged addresses. A re-engagement send to people who haven't heard from you in a year or more. Many will report it, and some old addresses have been turned into spam traps.
  4. A bad link domain. A URL shortener, shared tracking domain or affiliate domain in the message has its own poor reputation. Domain blocklists like Spamhaus DBL can be a sign of this.
  5. A shared IP with bad neighbors. Google notes that every sender on a shared IP affects the others.

How to fix it

  1. Stop the stream that's being blocked. Don't keep sending the same campaign to Gmail hoping some gets through. Every rejected message is more negative data.
  2. Check authentication first. Run your domain through the email checker and confirm SPF, DKIM and DMARC pass and align. It's rarely the cause of 5.7.1, but you can't make a mitigation request while you're out of compliance, and it takes five minutes to rule out.
  3. Look at Postmaster Tools. Check your user-reported spam rate and the compliance status dashboard. If spam rate is the problem, the spam rate threshold explainer covers what the numbers mean.
  4. Find the source. Which list, segment, acquisition source or campaign started this? Compare bounce timing to what you changed. A new list source or a re-engagement send is the usual answer.
  5. Remove the bad data. Drop purchased or unconfirmed addresses entirely. Suppress anyone who hasn't engaged in a long time. Don't just pause them; take them out of the Gmail stream.
  6. Check every domain in the message. Your From domain, links, images and tracking domains. Replace shorteners and shared tracking domains with a branded domain you control. The blocklist playbook covers domain listings.
  7. Restart small, to your best recipients. Send only to people who opened or clicked recently, at modest volume, and increase gradually as bounces stop and spam rate stays low.
  8. Request mitigation only when you qualify. Google's Sender Contact Form is for senders who meet the sender guidelines and still see excessive spam classification. Google's FAQ says senders above a 0.3% spam rate aren't eligible for mitigation until they've stayed below 0.3% for 7 consecutive days. Include full headers from a recent message.
⚠️
Switching to a new domain or new IPs to escape a 5.7.1 block tends to fail. The same list and the same practices produce the same reports, and you burn the new reputation too.

How to confirm it's fixed

The first sign is that 5.7.1 rejections stop for the restarted, engaged segment. Then watch two things over the next weeks: Gmail bounces in your logs as you widen the audience, and spam rate in Postmaster Tools. Use a few real Gmail seed accounts to check whether mail is reaching the inbox or merely being accepted into spam. Recovery isn't instant. Google says improvements to spam rate take time to show in delivery.

How to keep it from coming back

  • Collect consent clearly and keep a record of where each address came from.
  • Run a sunset policy so unengaged recipients stop getting mail.
  • Keep spam rate below 0.1% and watch it weekly, not just during incidents.
  • Use one-click unsubscribe and an obvious unsubscribe link. People who can't find the unsubscribe link press "report spam" instead.

When to get help

If you've cleaned the list and restarted small and Gmail is still rejecting your best recipients, or you can't find what changed, an outside review of your data sources and sending history usually finds it faster. Get in touch.

FAQ

Is Gmail's 5.7.1 a blacklist?

Not in the usual sense. It's Gmail's internal reputation system. You won't find it on any blacklist checker, and there's no removal form. Public blocklists can contribute to Gmail's view of you, but this bounce is Gmail's own decision.

How long does a Gmail 5.7.1 block last?

Google doesn't publish a timeline. It lasts as long as your reputation stays bad, and it improves as Gmail sees good data from your mail. Fixing the cause and sending only to engaged recipients is what moves it.

Only some messages get 5.7.1 and others deliver. Why?

Gmail judges messages, not just senders. Your reputation may be borderline, with the worst campaigns, segments or links pushing specific messages over the line. Look at which campaigns and which links the blocked messages have in common.

Can my ESP get the block lifted?

Not directly. Your ESP can confirm whether a shared IP is involved and move you to cleaner infrastructure, but Gmail doesn't take allowlist requests, and a domain reputation problem follows you to any ESP.

Sources

Related guides

Still stuck?

Some deliverability problems take an experienced eye to untangle. Tell me what you're seeing and I'll tell you what I'd check first. The first 30-minute call is free.