Email Bounce Error Codes Explained: 550, 554, 421 and More

Understanding SMTP Bounce Error Codes

Email bounce error codes are the standardized responses that receiving mail servers return when a message cannot be delivered. Every email administrator encounters these codes — understanding them is essential for diagnosing delivery failures, authentication problems, and reputation issues. These codes follow a standardized format defined in RFC 5321 (basic codes) and RFC 3463 (enhanced codes).

Basic Code Format (3 digits)

The first digit tells you the category:

• 2xx — Success (message accepted)
• 4xx — Temporary failure (try again later)
• 5xx — Permanent failure (do not retry — the message will not be accepted)

Enhanced Code Format (x.y.z)

Enhanced status codes provide more specific information:

• x.0.z — Other/undefined
• x.1.z — Addressing status (mailbox, system)
• x.2.z — Mailbox status (full, disabled)
• x.3.z — Mail system status
• x.4.z — Network and routing
• x.5.z — Mail delivery protocol
• x.6.z — Media conversion
• x.7.z — Security or policy (authentication, permissions)

Permanent Bounce Codes (5xx) — Your Message Was Rejected

550 5.1.1 — User Unknown / Mailbox Not Found

What it means: The recipient email address does not exist at the destination server.

Common causes:

• Typo in the email address
• The account was deleted or deactivated
• The domain exists but does not have mail service configured

Fix: Verify the email address is correct. If the address was valid recently, the account may have been removed. Contact the recipient through another channel.

550 5.1.2 — Bad Destination System

What it means: The destination mail system does not exist or cannot be reached.

Common causes:

• The domain has no MX records
• The domain has expired or been deleted
• DNS configuration is broken

Fix: Use the mxio MX Lookup on the recipient's domain to check if mail servers are configured.

550 5.4.1 — Routing or Host Unreachable

What it means: The destination host could not be reached or routing to the recipient failed.

Common causes:

• The destination mail server is unreachable or not responding
• DNS routing failure (MX points to a host that does not accept mail)
• Forwarding loop or routing misconfiguration

550 5.7.1 — Relaying Denied / Message Rejected

What it means: The receiving server refused your message based on policy. This is a broad code used for many types of rejection.

Common causes:

• Your IP is on a blacklist — use the mxio Blacklist Check
• SPF authentication failed — check with the mxio SPF Checker
• DMARC policy rejection
• Content filtering triggered

Fix: Analyze the full bounce message for the specific reason. The text after the code usually explains why.

550 5.7.23 — SPF Validation Failed (Microsoft)

What it means: Microsoft 365 rejected your email because SPF authentication failed.

Fix: See Fix Microsoft 365 Error 550 5.7.23 for the complete troubleshooting guide.

550 5.7.26 — DMARC Rejection (Gmail)

What it means: Gmail rejected your email because it failed DMARC authentication and the sending domain has a p=reject policy.

Fix: See Fix Gmail Error 550 5.7.26 for the complete troubleshooting guide.

550 5.7.708 — IP Blocked (Microsoft)

What it means: Microsoft's Exchange Online Protection (EOP) is blocking your IP address.

Fix: See Fix Microsoft 365 Error 550 5.7.708 for the delisting process.

552 5.2.2 — Mailbox Full

What it means: The recipient's mailbox has reached its storage quota.

Fix: Nothing you can do on your end. The recipient needs to clean up their mailbox or their admin needs to increase the quota. Retry later.

553 5.1.3 — Malformed Address

What it means: The email address has invalid syntax.

Common causes:

• Special characters in the address
• Missing @ symbol or domain part
• Extra spaces in the address

554 5.7.1 — Message Rejected (General)

What it means: The message was rejected for security or policy reasons. Servers use both 554 5.7.1 and 550 5.7.1 for policy rejections; the distinction between them varies by implementation.

Common causes:

• IP blocklisted at the connection level
• TLS requirement not met
• Connecting from a suspicious network range

Temporary Bounce Codes (4xx) — Try Again Later

421 4.7.0 — Temporary Rate Limit / Throttle

What it means: The receiving server is temporarily refusing connections, usually because you are sending too much too fast.

Common causes:

• Sending too many messages in a short period
• Gmail rate limiting for bulk senders
• Greylisting (intentional temporary rejection of first-time senders)

Fix: Your mail server should automatically retry. If it does not, check your MTA retry settings. For greylisting, the second attempt should succeed. For rate limiting, slow down your sending rate.

421 4.7.28 — Connection Rate Limit (Gmail)

What it means: Gmail is throttling your IP because it is sending too many connections.

Fix: Reduce the number of simultaneous connections. Space out your sends. If you are sending legitimate bulk email, ensure you are following the bulk sender requirements.

450 4.2.1 — Mailbox Temporarily Unavailable

What it means: The recipient's mailbox cannot accept mail right now but may be available later.

Common causes:

• Server maintenance
• Temporary storage issues
• Greylisting

451 4.3.0 — Internal Server Error

What it means: The receiving server had an internal error processing your message.

Fix: Retry. If it persists, the problem is on the receiving end.

452 4.5.3 — Too Many Recipients

What it means: You're trying to send to too many recipients in a single SMTP transaction.

Fix: Break your sends into smaller batches. Most servers limit to 100-500 recipients per connection.

Authentication-Related Bounce Codes

These codes specifically relate to SPF, DKIM, and DMARC failures. For a complete overview of how these protocols work together, see the Email Authentication Guide.

For any authentication error, start by checking:

1. Use the mxio SPF Checker — Is the record valid? Are all senders included?
2. Use the mxio DKIM Checker — Is the key published? Is the selector correct?
3. Use the mxio DMARC Checker — What is your policy? Is alignment configured?

If SPF lookups are causing failures because your record exceeds the 10-lookup limit, mxio's Managed SPF resolves this automatically through SPF flattening. Set up domain health monitoring to alert you when authentication records change or degrade.

How to Read a Bounce Message

When you receive a bounce (NDR — Non-Delivery Report), it typically contains:

1. The error code — The 3-digit and enhanced status code
2. A human-readable message — Varies by provider
3. The original message headers — Paste these into the mxio Header Analyzer for detailed analysis
4. The timestamp — When the failure occurred

Look past the generic "delivery failed" text and find the specific status code. That's what tells you the actual problem.

Quick Reference Table

Related Articles

• Gmail Error 550 5.7.26 — DMARC rejection by Gmail
• Microsoft Error 550 5.7.23 — SPF failure at Microsoft
• Microsoft Error 550 5.7.708 — IP blocked by EOP
• Emails Going to Spam — When email arrives but goes to junk
• Blacklisted IP: How to Get Delisted — When your IP is on a blocklist
• Complete Email Authentication Guide — How SPF, DKIM, and DMARC work together
• Blacklist Recovery Guide — Step-by-step IP reputation repair
• Why Is DMARC Failing? — Troubleshooting DMARC authentication failures