What each Gmail 550 5.7.1 bounce means (likely unsolicited email, low IP or domain reputation, IPv6 PTR, RFC 5322 header errors, relay and policy blocks), how to tell them apart and how to fix each one.
Home › Guides › Gmail 550 5.7.1
Last updated 18 November 2026
Gmail uses 550 5.7.1 for many different permanent rejections. The words after the code tell you which one you have:
Every Gmail error ends in gsmtp. If it also says gcdp, a Google Workspace admin on the receiving side made a custom rule that blocked it.
All texts below are from Google's SMTP error reference. Words in italics are placeholders.
| Group | Text after 550 5.7.1 | What to fix |
|---|---|---|
| Spam / reputation | This message is likely unsolicited email. To reduce the amount of spam sent to Gmail, this message has been blocked. | Spam rate, list quality, authentication, content. See below. |
| Spam / reputation | This message is likely suspicious due to the very low reputation of the sending IP address. To best protect our users from spam, the message has been blocked. | The IP: shared IP neighbours, blocklists, PTR, volume spikes. |
| Spam / reputation | This message is likely suspicious due to the very low reputation of the sending domain. To best protect our users from spam, the message has been blocked. | The domain: spam complaints, authentication, Safe Browsing status. |
| IPv6 | This message does not meet IPv6 sending guidelines regarding PTR records and authentication. | PTR for the IPv6 address plus SPF or DKIM. |
| Message format | Messages missing a valid address in the From: header, or having no From: header, are not accepted. | The program or service that builds the message. Google's guidelines: one address in From:, a valid Message-ID on every message, and single-instance headers (From:, To:, Subject:, Date:) only once. |
| Message format | Messages missing a valid Message-ID: header are not accepted. | |
| Message format | Messages with multiple addresses in the From: header are not accepted. | |
| Message format | This message is not RFC 5322 compliant because it has duplicate headers. | |
| Message format | This message is not RFC 5322 compliant because the From: header is missing. | |
| Message format | This message is not RFC 5322 compliant because it has multiple From: headers. | |
| Message format | This message is not RFC 5322 compliant because the From: header has a non-compliant domain name. | |
| Message format | Encoded-word syntax is not permitted in message header header-name. / This message is not RFC 5322 compliant. There are multiple header-name headers. | |
| Message format | The message contains a unicode character in a disallowed header. | |
| Sending IP | The IP you're using to send email is not authorized to send email directly to our servers. Use the SMTP relay at your service provider instead. | Send through your provider's relay or your own mail server. |
| Rate | This email has been rate limited. | Volume. See the Gmail 4.7.28 rate limit guide. |
| Recipient policy | The user or domain that you are sending to (or from) has a policy that prohibits the email that you sent. Contact your domain administrator for assistance. | Rules set by the recipient's (or your own) Google Workspace admin. |
| Workspace SMTP relay | Invalid credentials for relay ip-address. | Relay settings (IP, SMTP AUTH or HELO domain); see below. |
| Workspace SMTP relay | Daily SMTP relay sending limit exceeded for this customer. | Your Workspace relay quota; ask your admin. |
Google's example of a custom rule bounce is 550 5.7.1 This message violates example.com email policy. - gcdp sessionid - gsmtp. Authentication failures (SPF, DKIM, DMARC) use 5.7.26 and related codes, covered in Gmail 550 5.7.26.
Google's help page on blocked messages says Gmail blocks some mail that looks like spam, and that a message "might be blocked if it contains words that look like spam or if the sender has a history of sending spam." There is no form to unblock a sender; Google says it doesn't accept allowlist requests from email providers. Work through the sender guidelines instead:
550 5.7.1 can happen when the IP is on an IP suspended list, for example a shared IP with a poor reputation. See who owns the IP with the ASN IP Lookup.spf=pass, dkim=pass and dmarc=pass in its headers.Need SPF, DMARC and MX checks across a whole client list? Run the Bulk SPF / DMARC / MX Auditor on Apify ($2 per 1,000 domains).
Check SPF, DKIM and DMARC together with the Email Deliverability Checker, inspect a test message with the Email Header Analyzer, check PTR and forward DNS with DNS Lookup, find who operates an IP with the ASN IP Lookup, and check records with the SPF Record Checker and DMARC Record Checker. Related guides: Gmail 550 5.7.26, Gmail 421 4.7.28 rate limited, bulk sender rules and Outlook.com 550 5.7.515.
It is a permanent rejection, and Gmail uses the same code for many reasons. Read the text after the code: likely unsolicited email and low reputation mean a spam or reputation block, RFC 5322 and Message-ID texts mean a malformed message, and relay or policy texts mean a configuration or recipient rule.
Lower your spam rate (below 0.10% in Postmaster Tools, never 0.30%), authenticate with SPF, DKIM and DMARC, make sure the sending IP has matching PTR and forward DNS, send only to people who opted in, and ramp volume slowly. Google does not accept allowlist requests.
Google says it does not accept allowlist requests from email providers and cannot make exceptions for IPs that are not authorized to send. The fix is to meet the sender guidelines and let reputation recover, which takes time.
gcdp stands for Google Custom Domain Policies. It means a Google Workspace administrator created a rule that rejected the message, so the recipient organization has to change or explain the rule.
The message has a header problem: no From header, more than one From header or address, a missing Message-ID, or a duplicated single-instance header such as Subject or Date. Fix the software that builds the message.
Runbooks, checklists and helpdesk templates: IT Admin Packs on Gumroad.