Master Bounce Handling

An email bounce is a message that couldn't be delivered. The receiving server rejected it and sent back an error explaining why.

Bounces are classified into two main types:

Hard bounces are permanent failures. The email address doesn't exist, the domain is invalid, or the recipient server definitively refuses delivery. These addresses should be removed from your list immediately.

Soft bounces are temporary failures. The mailbox is full, the server is temporarily unavailable, the message is too large, or there's a temporary policy block. The address might work later.

Bounce messages contain diagnostic information. SMTP error codes and text explanations tell you what went wrong. A 550 "user unknown" is clear. A 451 "try again later" suggests a temporary issue.

Bounce handling matters for deliverability. Continuing to send to addresses that bounce damages reputation. High bounce rates signal poor list hygiene. Remove hard bounces immediately. Monitor soft bounces and remove addresses that consistently fail.

Your ESP typically processes bounces automatically. Hard bounces are usually suppressed immediately. Soft bounces might be retried a few times before suppression. Understand your platform's policies.

The difference is permanence. Hard bounces won't resolve. Soft bounces might.

Hard bounces indicate permanent delivery failure:

The email address doesn't exist (user unknown)
The domain doesn't exist or has no mail server
The recipient has permanently blocked you
The address was valid but has been deactivated

Hard bounced addresses should be immediately removed from your list. Continuing to send wastes resources and damages reputation.

Soft bounces indicate temporary delivery failure:

The mailbox is full and can't accept more messages
The receiving server is temporarily unavailable
The message is too large for the recipient's limits
Rate limiting or temporary policy blocks

Soft bounced addresses might accept email later. Most systems retry soft bounces several times before giving up.

Classification isn't always clear. Some errors are ambiguous. A "mailbox full" might be temporary (vacation) or effectively permanent (abandoned account). Some ESPs convert repeated soft bounces to hard bounces after multiple failures.

Track your bounce rates. Industry average is under 2%. Rates above that suggest list quality problems. Rates dramatically above that indicate serious issues requiring immediate attention.

4xx SMTP codes indicate temporary, transient conditions:

The signal:

"I cannot accept this message right now, but try again later." The failure is not permanent. Conditions may change.

Common 4xx codes:

421: Service not available, closing connection. 450: Mailbox unavailable (busy or temporarily blocked). 451: Local error in processing. 452: Insufficient storage. 454: Temporary authentication failure.

Sender response:

Queue the message for retry. Use appropriate backoff intervals. Eventually succeed or convert to permanent failure.

Why temporary matters:

Do not suppress addresses on 4xx alone. Give the system time to recover. Track patterns that may indicate deeper issues.

4xx is a polite "not right now." The door is not closed; just try again later.

5xx SMTP codes indicate permanent, fatal conditions:

The signal:

"I will not accept this message. Do not retry." The failure is definitive. Retrying would be wasteful.

Common 5xx codes:

550: Mailbox not found or unavailable. 551: User not local. 552: Message exceeds size limit. 553: Mailbox name not allowed. 554: Transaction failed (generic).

Sender response:

Do not retry this message. Suppress the address (for mailbox-specific errors). Investigate and resolve (for sender-side issues).

Important distinction:

Some 5xx codes indicate recipient problems (suppress address). Others indicate sender problems (fix your configuration). Read the full error message for context.

5xx is a firm "no." Respect it and move on.

SMTP 452 indicates storage limitations:

What it means:

The receiving server or mailbox does not have enough storage. This could be a system-wide issue or specific to the recipient's mailbox.

Common causes:

Mailbox quota exceeded: User's inbox is full. Server disk full: System-wide storage issue. Message queue full: Too many messages waiting.

Typical message examples:

"452 Insufficient system storage" "452 Mailbox full" "452 Too many recipients"

Response:

Retry later. User may delete messages and free space. Persistent 452 on specific address may warrant escalation to soft-to-hard bounce conversion.

452 is a full parking lot. Wait for someone to leave, or accept that this destination may be permanently unavailable.

Hard bounces result from permanent conditions that will not change:

Address does not exist:

User never existed at this domain. User account was deleted. Typo created invalid address.

Domain issues:

Domain does not exist. Domain has no MX records. Domain not configured for email.

Permanent account status:

Account permanently disabled. Account converted to alias without forwarding. Mailbox abandoned and removed.

Policy-based permanent rejection:

Address or domain permanently blocklisted. Sender permanently banned. Content type never allowed.

Response to hard bounces:

Suppress immediately. Do not retry. Remove from active lists. Investigate source for list quality issues.

Hard bounces are closed doors. The destination simply does not exist or will never accept from you.

A bounce processor handles bounce messages systematically:

Core functions:

Receive: Collect incoming bounce messages (DSNs). Parse: Extract relevant information (codes, addresses, timestamps). Classify: Categorize by type (hard, soft, block, technical). Route: Trigger appropriate downstream actions.

Downstream actions:

Update suppression lists. Queue for retry (soft bounces). Alert on unusual patterns. Update CRM or database records. Generate reports and analytics.

Technical implementation:

Dedicated mailbox monitoring Return-Path addresses. Pattern matching against bounce dictionaries. Integration with ESP APIs. Real-time processing pipelines.

A bounce processor is the harbor's damage assessment team. It determines what went wrong and what to do about it.

High bounce rates directly damage sender reputation:

What ISPs conclude:

You are sending to invalid addresses. List quality is poor. Acquisition practices may be questionable. You are not maintaining your list.

Reputation impacts:

Immediate: Throttling and increased deferrals. Short-term: More messages filtered to spam. Long-term: Potential blocking and blocklisting.

Threshold concerns:

Hard bounce rates above 2%: Concerning. Above 5%: Serious reputation damage. Above 10%: May trigger ESP suspension.

Recovery difficulty:

Reputation damage accumulates. Takes sustained good behavior to recover. Prevention far easier than remediation.

Bounce rates are a report card on list quality. High rates tell ISPs you are not a careful sender.

Automated bounce suppression protects reputation programmatically:

How it works:

Bounce received and classified. Rules evaluated for suppression criteria. Address added to suppression list automatically. Future sends to address blocked.

Suppression triggers:

Hard bounce: Immediate suppression. Soft bounce threshold: After N consecutive failures. Block bounce: May or may not trigger, depending on rules. Manual: Complaint or request-based.

Implementation components:

Bounce classification engine. Rules engine for decisions. Suppression list database. Integration with sending systems.

Benefits:

Consistent, timely action. No human delay. Scalable to any volume. Protects reputation automatically.

Automation converts bounce intelligence into protective action. Speed and consistency beat manual processes.