Email Bounce Codes Explained: What 550, 421, and Other SMTP Errors Mean
Comprehensive guide to SMTP bounce codes and error messages. Learn what 550, 421, 452, and other email error codes mean and how to fix them.
When an email fails to deliver, you receive a bounce message with an error code. These codes tell you exactly what went wrong—if you know how to read them. Understanding bounce codes helps you diagnose delivery issues and take corrective action.
How SMTP Codes Work
SMTP (Simple Mail Transfer Protocol) uses three-digit codes to communicate status:
| First Digit | Category | Meaning |
|---|---|---|
| 2xx | Success | Action completed successfully |
| 4xx | Temporary failure | Try again later |
| 5xx | Permanent failure | Won't work—don't retry |
The second and third digits provide more specific information about the error.
Common 5xx Permanent Errors
550 - Requested Action Not Taken
The 550 error is the most common bounce code. It has many variations:
550 5.1.1 - User Unknown
550 5.1.1 The email account that you tried to reach does not exist
Meaning: The recipient email address doesn't exist.
Causes:
- Typo in email address
- Account was deleted
- Never existed
Fix: Verify the email address is correct. Remove from your list if invalid.
550 5.7.1 - Message Rejected
550 5.7.1 Message rejected per DMARC policy
Meaning: Your email failed authentication and the domain's policy requires rejection.
Causes:
- SPF failure
- DKIM failure
- DMARC policy violation
Fix: Check and fix your SPF, DKIM, and DMARC configuration.
550 SPF Check Failed
550 SPF check failed: IP not authorized
Meaning: The sending server IP isn't in the SPF record.
Causes:
- Sending from unlisted IP
- SPF record misconfigured
- Using a new email service not yet added to SPF
Fix: Add the sending IP or service to your SPF record.
550 5.7.26 - Unauthenticated Email
550 5.7.26 This message does not have authentication information
Meaning: Email lacks required authentication (common with Gmail).
Fix: Implement SPF, DKIM, and DMARC authentication.
551 - User Not Local
551 User not local; please try <forward@example.com>
Meaning: The server doesn't handle mail for this address but suggests an alternative.
Fix: Use the suggested forwarding address.
552 - Message Too Large
552 5.3.4 Message size exceeds fixed maximum message size
Meaning: Your email (including attachments) exceeds the size limit.
Typical limits:
- Gmail: 25MB
- Outlook: 25MB
- Yahoo: 25MB
Fix: Reduce attachment size or use a file sharing service.
553 - Mailbox Name Invalid
553 5.1.3 Invalid address format
Meaning: The email address format is invalid.
Causes:
- Missing @ symbol
- Invalid characters
- Malformed domain
Fix: Correct the email address format.
554 - Transaction Failed
554 5.7.1 Service unavailable; Client host blocked
Meaning: The receiving server rejected the entire transaction.
Common variations:
| Code | Meaning |
|---|---|
| 554 5.7.1 | IP blocked or blacklisted |
| 554 5.7.5 | DMARC permanent error |
| 554 5.7.9 | Sending without TLS when required |
Fix: Check blacklists, fix authentication, ensure TLS is enabled.
Common 4xx Temporary Errors
421 - Service Not Available
421 4.7.0 Try again later, closing connection
Meaning: Server is temporarily unavailable. Retry should work.
Causes:
- Server maintenance
- Temporary overload
- Rate limiting
Action: Wait and retry. Most email systems do this automatically.
450 - Mailbox Unavailable
450 4.2.1 Mailbox temporarily unavailable
Meaning: Mailbox exists but can't accept mail right now.
Causes:
- Mailbox is full
- Temporary server issue
- User over quota
Action: Retry later. Issue usually resolves on recipient's end.
451 - Local Error
451 4.3.0 Mail server temporarily rejected message
Meaning: The receiving server had a temporary internal error.
Causes:
- Server configuration issues
- Temporary system problems
- Anti-spam processing delays
Action: Automatic retry should succeed.
452 - Insufficient Storage
452 4.2.2 Over quota
Meaning: Recipient's mailbox is full.
Action: Wait for recipient to clear space. Your server will retry.
Enhanced Status Codes
Modern bounce messages include enhanced status codes (X.Y.Z format):
| Second Digit | Category | Examples |
|---|---|---|
| X.1.X | Address issues | User unknown, bad destination |
| X.2.X | Mailbox issues | Full, disabled, doesn't accept mail |
| X.3.X | System issues | Size limit, mail system full |
| X.4.X | Network issues | Routing problems, connection timeout |
| X.5.X | Protocol issues | Invalid commands, syntax errors |
| X.6.X | Content issues | Media issues, conversion problems |
| X.7.X | Security issues | Auth failures, encryption required |
Authentication-Related Codes
SPF Failures
| Code | Message | Meaning |
|---|---|---|
| 550 5.7.23 | SPF validation failed | IP not authorized |
| 550 5.7.24 | SPF permerror | SPF record has syntax error |
| 451 4.7.24 | SPF temperror | Temporary DNS issue |
DKIM Failures
| Code | Message | Meaning |
|---|---|---|
| 550 5.7.20 | DKIM failed | Signature invalid |
| 550 5.7.21 | DKIM permerror | DKIM record problem |
| 451 4.7.21 | DKIM temperror | Temporary DNS issue |
DMARC Failures
| Code | Message | Meaning |
|---|---|---|
| 550 5.7.1 | DMARC policy reject | Failed DMARC with p=reject |
| 550 5.7.5 | Permanent DMARC failure | Neither SPF nor DKIM aligned |
What to Do With Each Bounce Type
Identify hard vs soft bounces
5xx = hard bounce (permanent), 4xx = soft bounce (temporary)
Handle hard bounces immediately
Remove addresses that hard bounce—they won't work.
Monitor soft bounces
Soft bounces that persist become hard bounces after multiple attempts.
Fix authentication issues
5.7.x errors related to SPF/DKIM/DMARC need configuration fixes.
Check blacklists for IP blocks
550 errors mentioning "blocked" require blacklist investigation.
Provider-Specific Messages
Gmail
550-5.7.26 This mail is unauthenticated, which poses a security risk to the
sender and Gmail users
Gmail requires authentication. Set up SPF, DKIM, and DMARC.
Microsoft/Outlook
550 5.7.1 Service unavailable, Client host [IP] blocked using Spamhaus
Your IP is on a blacklist. Check and request removal.
Yahoo
553 5.7.1 [BL21] Connections will not be accepted from IP, because the
IP is in Spamhaus's list
Similar to Microsoft—blacklist issue.
Each provider phrases errors differently, but the numeric codes follow the same standard.
Reducing Bounces
For Hard Bounces (5xx)
- Validate email addresses — Use verification tools before sending
- Clean your list regularly — Remove addresses that bounce
- Use double opt-in — Confirms addresses are real
- Monitor bounce rates — High rates indicate list quality issues
For Soft Bounces (4xx)
- Implement proper retry logic — Most systems handle this automatically
- Don't hammer servers — Respect rate limits
- Convert persistent soft to hard — After 72 hours of failure, treat as hard bounce
For Authentication Errors
- Verify SPF configuration — Include all sending sources
- Confirm DKIM is signing — Check that keys are published
- Set up DMARC — Even at p=none for visibility
- Monitor authentication rates — Should be 100% pass
Check Your Email Authentication
Many bounce codes result from authentication failures. Verify your SPF, DKIM, and DMARC configuration.
Understanding bounce codes transforms cryptic error messages into actionable diagnostics. When you know what the code means, you can fix the underlying issue and get your emails delivered.