550 5.7.1: Gmail blocked likely unsolicited mail or low reputation
Gmail refused the message because it looks like unsolicited mail, or because the sending IP address or domain has a very low reputation.
550 5.7.1 This message is likely unsolicited email. To reduce the amount of spam sent to Gmail, this message has been blocked.
Gmail's text (without its closing link), as listed in Google's SMTP errors reference. Gmail's replies can run over several lines; RFC 5321 says every line except the last starts with the code followed by a hyphen, so the same error can appear as 550-5.7.1.
What 550 5.7.1 means
Gmail uses 550 5.7.1 for many reasons, from admin policies to malformed headers. This entry covers the three reputation and spam texts in Google's reference:
- "This message is likely unsolicited email."
- "This message is likely suspicious due to the very low reputation of the sending IP address."
- "This message is likely suspicious due to the very low reputation of the sending domain."
These are permanent rejections, so the messages bounced. Gmail decides based on the history of mail from your IP and domain: how recipients react, how much you send and how consistently, and whether you meet its sender guidelines (authentication, valid reverse DNS, TLS, low spam rates, easy unsubscribing for bulk mail). Gmail's guidelines ask senders to keep the spam rate reported in Postmaster Tools below 0.3%.
Reputation can't be repaired by a single setting. Fix the basics, find out why recipients don't want the mail, then send less, to engaged recipients, and let reputation recover over time. If the domain reputation is low and you never send bulk mail, check for a compromised mailbox or web form.
Likely causes
- High spam complaint rates from Gmail users.
- Sending to old, purchased or unconfirmed lists.
- A compromised account or form sending spam from your IP or domain.
- Missing authentication or reverse DNS, which makes the mail look less trustworthy.
- Sudden volume spikes from an IP or domain with little history.
How to fix it
If you sent the message
- Make sure SPF, DKIM and DMARC pass and your sending IP has valid reverse DNS.
- Check for compromised accounts and forms; stop any spam at the source.
- Send only to recipients who asked for your mail; remove inactive and bouncing addresses.
- Add one-click unsubscribe to marketing mail and honor it quickly.
- Monitor spam rate and reputation in Google Postmaster Tools while you recover.
If you're the recipient or their admin
- Gmail users can mark a wanted sender's messages as not spam, but that doesn't override a 550 rejection at the server; the sender needs to fix their reputation.
Frequently asked questions
How do I fix a low sending reputation with Gmail?
Meet Google's sender guidelines (authentication, reverse DNS, TLS, low spam rate), stop sending to people who didn't ask for your mail, and keep volume steady. Reputation recovers gradually as recipients engage with your mail instead of reporting it.
Is this the same as being on a blocklist?
Not exactly. Gmail rates IPs and domains itself. A public blocklist listing can come from the same underlying problem, though, so it's worth checking.
Sources
- Gmail SMTP errors and codes (Google Workspace Admin Help)
- Email sender guidelines (Gmail Help)
- RFC 3463: Enhanced Mail System Status Codes
- RFC 5321, section 4.2: SMTP replies (multiline reply format)
Provider messages are quoted as the provider publishes them. Servers can change their wording, so the bounce you received may differ slightly.
Related codes
- 421 4.7.28 421 4.7.28: Gmail has detected an unusual rate of email
- 421 4.7.0 421 4.7.0: Gmail is temporarily deferring your mail
- 550 5.7.1 550 5.7.1: delivery not authorized, message refused
- 550 5.7.26 550 5.7.26: Gmail blocked an unauthenticated message
- 550 5.4.5 550 5.4.5: daily user sending limit exceeded
Related guides
Gmail, Yahoo and Microsoft bulk sender requirements explained
What Gmail, Yahoo and Outlook.com require from bulk senders: SPF, DKIM, DMARC, alignment, one-click unsubscribe and spam rates, with the real dates and limits.
9 min read Running email day to dayWhy did this email go to spam or quarantine?
Why an email went to the spam folder or quarantine, what each spam verdict means, how to find the reason in the headers, and how to fix or release the message.
9 min read Running email day to dayHow to get your domain or IP removed from an email blacklist
How to check if your mail server IP or domain is on a DNS blocklist, find the real cause, and request removal from Spamhaus, SpamCop, Barracuda and Microsoft.
9 min read