Skip to main content

Email Bounce Code Reference

An email bounce occurs when a message cannot be delivered to the recipient. Every bounce carries an SMTP response code that tells you exactly why the delivery failed and what to do about it.

This guide covers:

  • SMTP 4xx codes — soft bounces (temporary failures, retryable)

  • SMTP 5xx codes — hard bounces (permanent failures)

  • Enhanced delivery status codes (RFC 3463 — X.Y.Z format)

  • ISP-specific bounce codes (Microsoft, Gmail, Yahoo)

  • Bounce message interpretation

  • Recommended bounce rate thresholds

  • Relevant resources and tools

Quick decision guide

Before you look at individual codes, use this rule of thumb:

Code range

Bounce type

4xx

Soft bounce (temporary)

Retry? Yes

List action: Keep the address. Remove it only if the soft bounces persist (5 or more soft bounces on the same address).

5xx

Hard bounce (permanent)

Retry? No

List action: Remove the address immediately and add it to the suppression list.

5.X.X

Enhanced status (RFC 3463)

Retry? Depends on the subcode

List action: Follow the code-specific action in Enhanced status codes.

SMTP 4xx: Soft bounce codes (temporary)

4xx codes indicate a temporary failure. The sending server automatically retries delivery. These codes do not require immediate list cleanup, but repeated soft bounces to the same address must be treated as hard bounces after 5 or more failures.

Code

Name

421

Service temporarily unavailable

What it means: The receiving server is busy or temporarily down. The mail is retried.

Recommended action: The ESP retries automatically. If it persists beyond 24 hours, there may be an issue with the recipient server.

450

Mailbox unavailable (temporary)

What it means: The recipient mailbox is temporarily unavailable. It may be locked or over quota.

Recommended action: Retry later. No action is needed unless the pattern repeats.

451

Local error in processing

What it means: A server-side processing error, often a spam filter or policy hold.

Recommended action: Monitor it. If it is domain-wide, check the sending IP reputation.

452

Insufficient storage or quota exceeded

What it means: The receiving server or mailbox has run out of storage space.

Recommended action: Retry later. This is not a sender-side issue.

455

Server unable to accept parameters

What it means: The server cannot handle the current request parameters, due to a timing or resource issue.

Recommended action: The ESP retries automatically. This may indicate rate limiting or resource overload.

SMTP 5xx: Hard bounce codes (permanent)

Never retry a 5xx bounce

5xx codes are permanent failures. Remove the address from your active list immediately and add it to the suppression list. Repeated sending to hard-bounced addresses damages your sender reputation significantly.

Code

Name

500

Syntax error or command unrecognised

What it means: The server could not parse the command sent. This is usually a client-side SMTP bug.

Recommended action: Review the SMTP client implementation. This is rare in modern ESPs.

501

Bad parameters or address syntax error

What it means: The email address has an invalid format, such as a missing domain or illegal characters.

Recommended action: Remove the address from the list. Validate email addresses before sending.

502

Command not implemented

What it means: The server received a command it does not support.

Recommended action: Contact Blueshift Deliverability for further diagnosis.

503

Bad sequence of commands

What it means: The SMTP commands were sent in the wrong order.

Recommended action: This is an ESP-level issue. It rarely happens with Blueshift.

504

Command parameter not implemented

What it means: A specific parameter in the SMTP command is not supported.

Recommended action: This is an ESP compatibility issue and is rarely seen. Contact Blueshift Deliverability for further diagnosis.

510

Bad email address

What it means: The email address does not exist or is malformed.

Recommended action: Suppress the address from the list immediately.

511

Bad email address

What it means: The address is invalid. This is very similar to 510.

Recommended action: Suppress the address from the list immediately.

512

DNS error or domain not found

What it means: The recipient domain does not exist or has no MX record.

Recommended action: Suppress the address. The domain is dead or invalid.

513

Address type incorrect

What it means: There is an address format or type mismatch.

Recommended action: Validate and remove invalid addresses.

521

Domain does not accept mail

What it means: The receiving domain explicitly rejects all incoming mail.

Recommended action: Suppress the address. The domain may be parked or decommissioned.

522

Recipient has exceeded mailbox limit

What it means: The mailbox is permanently full. Some systems treat this as a hard bounce.

Recommended action: Suppress the address. It is functionally inactive.

523

Recipient exceeds size limit

What it means: The message size exceeds the limit allowed by the recipient.

Recommended action: Reduce the email size or segment large attachments.

541

Rejected — spam or policy

What it means: The message was blocked due to spam content or a sender policy violation.

Recommended action: Review the content and contact Blueshift Deliverability for further diagnosis.

550

Mailbox unavailable or does not exist

What it means: The most common hard bounce. The recipient address does not exist.

Recommended action: Suppress the address from the list immediately.

551

User not local, try forwarding

What it means: The recipient is not local and the server suggests a forwarding address.

Recommended action: Update the address if a forwarding address is given. Otherwise, remove it.

552

Mailbox full or storage exceeded (permanent)

What it means: The mailbox is permanently over quota. Many ESPs treat this as a hard bounce.

Recommended action: Suppress the address. The account is likely abandoned.

553

Mailbox name not allowed

What it means: The recipient address violates the server naming rules.

Recommended action: Suppress the address. It is invalid.

554

Transaction failed or message rejected

What it means: A catch-all rejection for spam, blacklist, policy, or content blocks.

Recommended action: Contact Blueshift Deliverability for further diagnosis.

556

Domain does not accept mail

What it means: Similar to 521. The domain actively rejects all mail.

Recommended action: Suppress the address.

557

Too many recipients

What it means: There are too many recipients in a single send. The batch size is exceeded.

Recommended action: Reduce the number of recipients per message and segment your sends.

559

Authentication required

What it means: The recipient server requires au­then­ti­ca­tion from the sender.

Recommended action: Ensure SPF, DKIM, and DMARC are all configured properly. Contact Blueshift Deliverability for further diagnosis.

Enhanced status codes (RFC 3463, X.Y.Z format)

Modern mail servers return enhanced status codes in the X.Y.Z format alongside the standard three-digit SMTP code. These provide much more precise failure reasons and are increasingly used by Gmail, Microsoft, and Yahoo to communicate policy decisions.

Format breakdown

  • X = Class — 2 (success), 4 (transient), 5 (permanent)

  • Y = Subject — 1 (addressing), 2 (mailbox), 3 (mail system), 4 (network), 5 (protocol), 7 (policy)

  • Z = Detail code

Code

Name

5.1.0

Address rejected (generic)

What it means: A generic address rejection without a specific reason.

Recommended action: Review the full DSN message for details, or contact Blueshift Deliverability for further diagnosis.

5.1.1

Bad destination mailbox address

What it means: The address does not exist.

Recommended action: Hard remove the address immediately.

5.1.2

Bad destination mailbox address syntax

What it means: The address syntax is malformed.

Recommended action: Fix or remove the address.

5.1.3

Bad destination mailbox address syntax

What it means: Bad address syntax, similar to 5.1.2.

Recommended action: Remove the address.

5.1.6

Destination mailbox has moved, no forwarding

What it means: The mailbox has moved with no forwarding address.

Recommended action: Remove the address. Check for an updated address through other channels.

5.2.1

Mailbox disabled or not accepting messages

What it means: The account exists but is disabled.

Recommended action: Treat it as a hard bounce and remove the address from the list.

5.2.2

Mailbox full

What it means: The mailbox storage quota is exceeded.

Recommended action: Treat it as a soft bounce if temporary. Suppress the address if it persists across 5 or more retries.

5.2.3

Message length exceeds administrative limit

What it means: The message is too large for the recipient server.

Recommended action: Reduce the email size and avoid heavy attachments.

5.3.4

Message too large for system

What it means: The system-wide size limit is exceeded.

Recommended action: Revisit your message to reduce its size.

5.4.1

No answer from host

What it means: There is no SMTP response from the destination server.

Recommended action: Retry. This could be a network or DNS issue.

5.4.4

Cannot route: invalid domain

What it means: Routing failed because the domain does not resolve.

Recommended action: Suppress the address. The domain is dead.

5.5.0

Other or undefined protocol status

What it means: An unclassified SMTP protocol error.

Recommended action: Review the full DSN for context, or contact Blueshift Deliverability for further diagnosis.

5.7.1

Delivery not authorised or policy restriction

What it means: The sending IP or domain is blocked by policy.

Recommended action: Check IP blacklists, SPF, DKIM, and DMARC. Warm up the IP if it is new. Contact Blueshift Deliverability for further diagnosis.

5.7.9

Message does not meet IPv6 sending guideline

What it means: Google: the IPv6 PTR record is missing or mismatched.

Recommended action: Ensure the IPv6 PTR record matches the sending hostname.

5.7.23

SPF validation failure (Microsoft)

What it means: Microsoft rejected the message because the sending domain's SPF record does not authorise the sending IP. The SPF lookup on the envelope-from (Return-Path) domain failed because the IP is not listed, the record has a syntax error, or too many DNS lookups caused a permerror.

Recommended action:

  1. Check the SPF record for the envelope-from domain using dig TXT <domain>.

  2. Verify that the sending IP is explicitly included.

  3. Ensure the DNS lookups in the record are 10 or fewer. A permerror occurs if this is exceeded.

  4. Use SPF flattening if needed.

Microsoft is strict, so a neutral (~all) record may still trigger this.

5.7.25

DKIM validation failure (Microsoft)

What it means: Microsoft rejected the message because DKIM verification failed. The signature in the DKIM-Signature header did not validate against the public key published in DNS, or the signature was missing entirely.

Recommended action:

  1. Confirm that the DKIM selector is published correctly using dig TXT <selector>._domainkey.<domain>.

  2. Check that the signing domain (d= tag) aligns with the From: domain.

  3. Ensure that no intermediate server modifies the message body or headers after signing, as this breaks the hash.

  4. Verify that the key length is 1024 bits or more. 2048 bits is rec­om­mend­ed.

  5. If you use a shared ESP infrastructure, confirm that DKIM is configured at the subdomain level.

5.7.26

SPF and DKIM both unauthenticated (Gmail)

What it means: Gmail rejected the message because it failed both SPF and DKIM checks. Gmail requires at least one of the two to pass and align with the From: domain for DMARC compliance. If neither passes, Gmail treats the message as unauthenticated and rejects it outright rather than sending it to junk.

Recommended action:

  1. Fix SPF. Ensure the sending IP is authorised in the SPF record of the envelope-from domain.

  2. Fix DKIM. Ensure a valid DKIM signature is present and the d= tag aligns with the From: domain.

  3. At least one must pass with alignment for DMARC to pass.

  4. Check the DMARC policy. If it is p=reject, failing both will always result in this error.

  5. Run a test send through mail-tester.com or Google Admin Toolbox to confirm the au­then­ti­ca­tion results.

ISP-specific bounce codes

Major ISPs use standard SMTP codes, but the accompanying diagnostic message is ISP-specific and gives the real reason for the rejection. Always read the full DSN message, not just the numeric code.

For a list of email domains by ISP, see Email Domains by ISP and Mailbox Provider.

Microsoft, Outlook, and Hotmail

Microsoft publishes detailed sending requirements that cover authentication, list hygiene, complaint rates, and infrastructure setup. If you encounter repeated deferrals or blocks, review these guidelines before filing a remediation request through SNDS.

ISP or provider

Code

Microsoft / Outlook

550 5.4.1

Message: Recipient address rejected: access denied

Action or notes: The domain or IP is blocked by Microsoft. Contact Blueshift Deliverability for further support.

Microsoft / Outlook

550 5.7.1

Message: Unable to relay or policy rejection

Action or notes: The IP or domain is on the Microsoft block list. Contact Blueshift Deliverability for further support.

Microsoft / Outlook

421 4.7.0

Message: Temporarily deferred due to IP reputation

Action or notes: This is a soft block. Reduce the volume. Check Microsoft SNDS signals or contact Blueshift Deliverability.

Gmail and Google Workspace

Google enforces strict requirements around SPF, DKIM, and DMARC alignment. Non-compliance results in outright rejection, not just junking. Google's Email Sender Guidelines (updated February 2024) mandate one-click unsubscribe, a spam complaint rate below 0.3%, and valid authentication for all commercial senders. For a detailed walkthrough of Google's requirements and Blueshift's recommended configuration, refer to the Gmail sender guidelines.

ISP or provider

Code

Gmail / Google

550 5.7.26

Message: This mail is unauthenticated (SPF or DKIM)

Action or notes: Fix the au­then­ti­ca­tion. Google is strict on SPF, DKIM, and DMARC alignment. Contact Blueshift Deliverability for further support.

Gmail / Google

421-4.7.0

Message: IP sending limit exceeded or rate limited

Action or notes: Throttle your sends and warm up gradually. Do not blast high volumes.

Gmail / Google

550 5.2.1

Message: The email account is disabled

Action or notes: This is a hard bounce. Suppress the address immediately.

Yahoo! Mail and AOL

Yahoo follows an authentication posture similar to Gmail's and has jointly enforced bulk-sender requirements since early 2024. Senders must have valid SPF and DKIM, a published DMARC policy, and a functioning one-click unsubscribe (RFC 8058). Yahoo also enforces per-IP hourly sending limits that are not publicly documented, so throttling is the primary signal to watch. For Yahoo-specific configuration guidance used at Blueshift, refer to the Yahoo sender guidelines.

ISP or provider

Code

Yahoo / AOL

421 4.7.0

Message: Temporarily deferred; rate limit exceeded

Action or notes: Reduce the send rate at the campaign level. Yahoo enforces per-IP and per-hour limits.

Yahoo / AOL

550 5.7.9

Message: Message not accepted for policy reasons

Action or notes: This is an IP or domain reputation issue, or a content policy block.

Yahoo / AOL

554

Message: Message not allowed — spam or content blocked

Action or notes: Review the content, links, and unsubscribe mechanism.

Spamhaus, CBL, and DNSBL blocks

ISP or provider

Code

Spamhaus / CBL

550 5.7.1

Message: IP listed on Spamhaus SBL, XBL, or CBL

Action or notes: Investigate for a compromise or spam activity, then delist from Spamhaus. Contact Blueshift Deliverability for further support.

Bounce message interpretation

If you see this pattern

Investigate this

A high 550 or 5.1.1 rate

List hygiene issues. The addresses are old, bought, or not validated at capture.

A high 421 or 451 rate from a single ISP

Rate limiting or an IP reputation issue. Check the sending volume and IP warmup status.

554 or 541 across multiple ISPs

Content issues, or the IP or domain is on a blacklist. Run a DNSBL check and review the email content for spam signals.

5.7.26 from Gmail

An SPF or DKIM failure. Fix the au­then­ti­ca­tion records and verify DMARC alignment.

AUT-003 (DMARC reject)

The From: domain DMARC policy is p=reject and the au­then­ti­ca­tion is failing. Escalate to Deliverability.

Recommended bounce rate thresholds

These are Blueshift's recommended alert thresholds. Exceeding them triggers a deliverability review.

Metric

Healthy

Warning zone

Critical — action required

Hard bounce rate

Below 0.5%

0.5% – 2%

Above 2% — pause the campaign and investigate the list.

Soft bounce rate

Below 2%

2% – 5%

Above 5% — check ISP throttling and IP reputation.

Spam complaint rate

Below 0.08%

0.08% – 0.3%

Above 0.3% — review immediately. Gmail will block.

Relevant resources and tools

Did this answer your question?