Topic · Troubleshooting
SMTP 550 error
SMTP 550 is a permanent failure reply commonly used when a recipient or policy rejects a message.
How it works
The reply text and enhanced status code explain the actual cause more precisely.
What can go wrong
550 can mean invalid recipient, access denial or policy rejection; there is no single universal fix.
What to check or do
Capture the full SMTP transcript and route it to the relevant owner. Use the receiver’s enhanced code and text to distinguish causes.
Practical scenario
A server responds 550 5.7.1 to one sender but 550 5.1.1 to another. Although both are permanent 550 replies, the enhanced codes point toward policy rejection versus an invalid recipient; the remediation should differ.
Verification checklist
- Capture complete SMTP commands, reply text and enhanced status codes.
- Check address validity before blaming authentication.
- For policy errors, review SPF, DKIM, DMARC, sender reputation and receiver-specific guidance.
- Avoid blindly retrying permanent failures in a tight loop.
How to investigate SMTP 550 error
- Signal to investigate
- A recipient replies 550 5.1.1 while another rejects with 550 5.7.1.
- Evidence to collect
- Preserve the full enhanced status code and text, then distinguish invalid recipient from policy/authentication rejection.
- Common wrong conclusion
- The base 550 code is too broad to identify root cause by itself.
How to interpret the evidence
SMTP 550 is a permanent negative response class. The more informative part often lies in the enhanced code and receiver text: 5.1.1 suggests an invalid mailbox, while 5.7.1 often indicates policy or authorization, subject to server-specific wording. Treating all 550 responses as spam-filtering blocks can lead to needless DNS changes and retry storms.
What to change and how to verify it
Capture the complete server conversation and identify whether rejection happened at RCPT TO, DATA or a later stage. Route invalid-recipient failures to list cleanup; investigate policy failures through authentication, sender reputation and receiver documentation. Do not loop immediate retries for permanent failures.
# Preserve the full response, for example:
# 550 5.1.1 User unknown vs 550 5.7.1 Policy rejectionEducational example; not validated against your live infrastructure.Put this into practice
Run a focused check, then explore protection if your domain needs it.