
The SMTP 550 5.7.1 error means the receiving server permanently rejected your message for a security or policy reason. Unlike 550 5.1.1 (the address doesn't exist), 5.7.1 says the address may be fine but you're not allowed to deliver to it — because of the recipient's restrictions, an administrator's rule, your sending IP's reputation, missing authentication or a relay permission problem. This guide explains how to read the full error text, the common causes in Gmail, Microsoft 365 and other servers, and what senders and admins can do about each.
SMTP 550 5.7.1: The Short Answer
Likely cause | Clue in the error text | Who fixes it |
|---|---|---|
Recipient restrictions (only internal or approved senders) | "not authorized", "restricted" | Recipient's admin |
Administrator content or policy rule | Gmail: "gcdp" in the error | Recipient's admin |
Sender IP or domain on a blocklist | Blocklist name or "blocked" | Sender |
Authentication failure | SPF, DKIM or DMARC mentioned | Sender |
Relay not permitted | "relay access denied", "unable to relay" | Sender's mail server admin |
Group or public folder accepts only authenticated senders | "AuthRequired" | Recipient's admin |
💡 Read the full text
The digits are generic; the words after them tell you which cause you're facing.
550 5.7.1 in Microsoft 365 / Exchange Online
Microsoft's guide to fixing 550 5.7.1 says the information also applies to codes 5.7.0 through 5.7.999 and that typically the recipient or their email admin must fix it. Common Microsoft causes:
The recipient (often a group or public folder) is set to accept mail only from internal or authenticated senders.
The sender's source IP is on Microsoft's blocklist.
Mail flow rules or connectors in the recipient's tenant reject the message.
The sender's domain isn't fully set up in Microsoft 365 (MX or connector issues).
Related Microsoft codes: 5.7.515 (authentication requirements), 5.7.233 (tenant external rate limit) and 5.1.8 (restricted sender) — see SMTP error codes.
550 5.7.1 in Gmail / Google Workspace
Google notes that an error like "550 5.7.1 This message violates example.com email policy" with gcdp in the text comes from a custom rule created by the recipient's Google Workspace administrator (Gmail SMTP errors). Without gcdp, 5.7.x errors from Gmail usually relate to authentication, policy or reputation — check SPF, DKIM and DMARC against Google's sender guidelines.
Fixes If You're the Sender
Read the full error and note which server rejected you.
Check authentication: SPF includes your sender, DKIM signs, DMARC published and aligned (guide).
Check blocklists for your IP and domain (blacklist tools, removal).
Check relay settings if sending through your own server — you must authenticate to relay (SMTP relay vs server).
Contact the recipient another way if it's their restriction.
Pause the affected inbox if many recipients return 5.7.1.
Fixes If You're the Recipient's Admin
Allow external senders on the group, distribution list or public folder if appropriate.
Review mail flow rules, transport rules or Google content compliance rules that match the message.
Check connector and domain configuration.
Add trusted senders to allow lists carefully.
550 5.7.1 in Cold Email Campaigns
In outreach, a few 5.7.1 bounces usually mean individual companies block external or unknown senders — remove those contacts. Many 5.7.1 bounces across different companies point to your side: authentication, blocklisting or reputation. Then:
⏸️Pause the inbox or domain
Stop sending while you diagnose.
🔎Check auth and blocklists
Most common sender-side causes.
📋Check the list source
Spam traps and bad data trigger policy blocks.
🐢Resume slowly
Lower volume, best contacts first (recovery).
Example: Diagnosing a 5.7.1 Spike
Illustrative scenario. One outreach domain starts returning 550 5.7.1 from many Microsoft 365 recipients. The text mentions the sending IP. A blocklist check shows one listing; DKIM had also stopped signing after a DNS change. The team pauses the domain, restores the DKIM record, requests delisting, and resumes at a third of the previous volume on a fresh list segment. Other domains kept sending normally because volume was spread across inboxes (inbox sizing).
Prevent Policy Rejections
Most sender-side 5.7.1 errors trace back to:
🔐Authenticate every domain
SPF, DKIM and DMARC aligned (authentication guide, Google Workspace setup, Microsoft 365 setup).
🌐Use secondary sending domains
Keep your main domain out of cold outreach (domain setup, domain risks).
🔥Warm or start pre-warmed
Ramp gradually (warm-up guide) or use pre-warmed inboxes (pre-warmed vs fresh).
📉Keep per-inbox volume low
Scale with inboxes, not volume (safe sending limits, inbox sizing).
✅Verify every list
Bounces damage reputation fast (verification tools, list cleaning).
📊Monitor weekly
Spam rate, bounces and blocklists (Postmaster setup, blacklist tools).
Authentication Handled, Risk Spread
LiteMail | Fewer policy rejections
Fresh from $2.50/inbox
Official Google Workspace and Microsoft 365 inboxes for outreach
LiteMail provisions official Google Workspace and Microsoft 365 inboxes on secondary domains, configures SPF, DKIM and DMARC automatically and lists dedicated US and EU IPs. Automated DNS keeps SPF, DKIM and DMARC in place, and many inboxes per plan keep one blocked domain from stopping a campaign.
Strengths | Keep in mind |
|
|
Explore pricing, the inbox calculator, infrastructure, bulk inboxes and setups for agencies, SaaS and recruiters. Comparing providers? See Google Workspace vs Microsoft 365.
Keep policy blocks contained to one inbox — not your whole program. Get Pre-Warmed Inboxes →
Frequently Asked Questions
What does SMTP 550 5.7.1 mean?
The receiving server permanently rejected the message for a security or policy reason.
Is 550 5.7.1 my fault or the recipient's?
Either. Read the full text: recipient restrictions and admin rules are on their side; authentication, blocklists and relay issues are on yours.
What does gcdp mean in a Gmail 5.7.1 error?
It indicates the rejection came from a custom rule set by the recipient's Google Workspace admin.
How do I fix 550 5.7.1 in Microsoft 365?
Microsoft says the recipient or their admin usually needs to fix it, for example by allowing external senders.
Can authentication problems cause 550 5.7.1?
Yes. Check SPF, DKIM and DMARC alignment.
Can a blocklist cause 550 5.7.1?
Yes. Check your IP and domain on major blocklists.
What is 'relay access denied'?
Your server refused to relay because you weren't authenticated or authorised.
Should I retry after a 5.7.1 bounce?
Not until you've fixed or understood the cause; it's a permanent failure.
Stop Policy Blocks at the Source
Official Google Workspace and Microsoft 365 inboxes with automated SPF, DKIM and DMARC on dedicated US and EU IPs.
Automated DNS · Pre-warmed options · OAuth export
About LiteMail — LiteMail provides fresh and pre-warmed Google Workspace and Microsoft 365 inboxes for cold email outreach, with automated SPF, DKIM and DMARC setup, dedicated US and EU IPs, separate client workspaces and one-click OAuth export to Instantly, Smartlead, Lemlist and other sending tools. View pre-warmed inbox plans →
Related reading: SPF, DKIM and DMARC · Blacklist Removal · Outlook Troubleshooting · Microsoft 365 Setup Mistakes · Deliverability Recovery · Microsoft 365 Inboxes


