550-5.7.1 (unsolicited) high
Gmail 550-5.7.1 Message Blocked as Likely Unsolicited Mail
Gmail's spam filter judged the message likely unsolicited and blocked it on reputation or content grounds.
What you see
550-5.7.1 Our system has detected that this message is likely unsolicited mail. 550-5.7.1 To reduce the amount of spam sent to Gmail, this message has been blocked. 550 5.7.1 Please visit https://support.google.com/mail/?p=UnsolicitedMessageError for more information.
What’s actually happening
This is a hard bounce — 550, message rejected, gone. Gmail decided the mail looks like spam and refused it at the door, then pointed you at the UnsolicitedMessageError help page. It is not an authentication rejection; that's the separate 5.7.26 error about failing SPF/DKIM/DMARC. Here the headers can authenticate perfectly and Gmail still blocks on reputation and content. It often hits some recipients and not others, and tends to flare when you push volume or send from a fresh IP.
Common causes
- Poor sending-IP or domain reputation in Gmail's eyes — the single biggest driver, visible in Google Postmaster Tools.
- Spammy content signals: link shorteners, sketchy attachments, image-heavy/text-light bodies, deceptive subject lines.
- The IP or a domain in the message is on a blocklist Gmail consults (Spamhaus and similar).
- Sending without real opt-in — cold lists, scraped addresses, or recipients who never asked to hear from you.
- A volume spike or unwarmed IP that makes the traffic pattern itself look like a spam run.
How to fix it
- Open Google Postmaster Tools and read your reputationVerify your domain at postmaster.google.com and check the IP Reputation, Domain Reputation, and Spam Rate dashboards. 'Bad' or 'Low' reputation is your answer. Keep the user-reported spam rate under 0.1% and well clear of 0.3%, which is where Gmail starts blocking hard.
- Confirm SPF, DKIM, and DMARC all pass and alignThis isn't the 5.7.26 auth error, but weak authentication still drags reputation down. Make sure SPF passes, DKIM signs with your domain, DMARC aligns, and bulk senders meet Gmail's one-click List-Unsubscribe (RFC 8058) requirement.
- Check every relevant IP and domain against blocklistsLook up your sending IP and the domains in the message body on Spamhaus and a multi-RBL tool. If you're listed, follow each blocklist's delisting process and fix what got you listed before requesting removal.
- Clean up the content and the listDrop link shorteners and risky attachments, fix the text-to-image ratio, and write honest subject lines. Remove non-opt-in addresses, hard bounces, and dead contacts — Gmail's filter weighs engagement heavily, and mailing people who never engage is what trips it.
- Slow down and warm the IPIf this started after a volume jump or an IP change, throttle back and ramp gradually over days. A sudden surge from a low-history IP looks exactly like a spam campaign to Gmail's model.
Stop it recurring
Mail only opt-in recipients, watch Postmaster Tools spam rate and reputation daily, and warm new IPs slowly so Gmail never sees a spam-shaped traffic pattern.
Related errors