P H O T O N

CONSOLE

Loading

Deliverability Diagnostics

Hard Bounce vs. Soft Bounce
RFC Status Codes, Root Causes & Handling Protocols

Understand the critical architectural differences between 5xx permanent failures and 4xx transient retry errors to protect domain sender reputation.

6 min read • RFC 3463 & 5321 Standards • Automated Suppression
Direct Answer: Hard Bounce vs. Soft Bounce

A hard bounce (5xx status code) represents a permanent delivery failure (e.g., non-existent mailbox, invalid domain, recipient server refusal), requiring immediate and permanent address suppression. A soft bounce (4xx status code) is a temporary failure (e.g., full mailbox quota, transient server timeout, ISP rate-limiting) where retry queues attempt redelivery with exponential backoff over 72 hours before marking the message undeliverable.

1. Hard Bounce vs. Soft Bounce Comparison Matrix

Mailbox providers evaluate your bounce ratios on every outbound dispatch. Repeatedly retrying permanent hard bounces signals list neglect and botnet behavior, quickly triggering Gmail and Outlook spam filters.

Metric / Characteristic Hard Bounce (5xx) Soft Bounce (4xx)
Error Classification Permanent Failure (Unrecoverable) Transient / Temporary Failure (Recoverable)
Primary RFC Codes 550 5.1.1, 550 5.7.1, 554 5.4.4 451 4.2.2, 452 4.4.5, 421 4.7.0
Root Causes Non-existent email, deleted mailbox, dead MX record. Mailbox over quota, server greylisting, rate throttling.
MTA Action Required Instant, permanent suppression. Never retry. Exponential retry queue over 24 to 72 hours.
ISP Ceiling Benchmark Must stay strictly below 2.0%. Typically tolerated up to 5.0% during spikes.

2. Anatomy of a Hard Bounce (RFC 5xx Failures)

When an outbound MTA delivers mail to a recipient server and receives an immediate 5xx status response, the transaction is irreversibly terminated. Common examples include:

  • 550 5.1.1 User Unknown: The username or local mailbox does not exist at the target domain.
  • 550 5.1.2 Host Unknown: The destination domain has no valid MX records published in DNS.
  • 554 5.7.1 Relay Access Denied: Recipient server explicitly refuses to accept mail from unauthenticated sources.

3. Anatomy of a Soft Bounce (RFC 4xx Failures)

Soft bounces occur when the recipient mailbox is valid, but technical hurdles prevent delivery at the exact moment of connection:

  • 452 4.2.2 Mailbox Full: The recipient's storage quota is temporarily exceeded.
  • 451 4.7.1 Greylisting: The receiving server temporarily defers unknown senders to verify RFC retry compliance.
  • 421 4.7.0 Connection Throttled: The recipient ISP (e.g. Yahoo or Outlook) is rate-limiting your IP pool due to volume spikes.

4. Exponential Backoff & Automated Suppression

Photon Console utilizes automated queue workers with exponential backoff retry schedules for 4xx deferrals. If an email soft bounces, our MTA holds the message and attempts redelivery:

# PhotonRelay Queue Backoff Schedule (RFC 5321 Retries) Initial Attempt: Immediate (T+0s) Retry 1: T + 15 minutes (Overcomes transient ISP greylisting) Retry 2: T + 60 minutes Retry 3: T + 4 hours Retry 4: T + 12 hours Final Retry: T + 48 hours (Marked as Hard Defect if undelivered)

5. ISP Thresholds & Automated Circuit Breakers

Critical Deliverability Threshold: Google and Yahoo enforce a strict hard bounce threshold of <2.0%. A single unscrubbed batch containing 10% invalid addresses can permanently degrade your domain reputation tier in Google Postmaster Tools.

6. Frequently Asked Questions

Should I immediately delete email addresses that soft bounce?

No. Soft bounces are temporary issues such as a full mailbox or transient server timeout. Photon Console automatically retries delivery with exponential backoff over 72 hours. An address should only be suppressed if it consistently soft bounces across 3 to 5 separate campaigns over 14 days.

What is the industry benchmark ceiling for hard bounce rates?

The industry benchmark for hard bounce rates is strictly under 2.0%. A bounce rate exceeding 5.0% will cause mailbox providers like Google and Outlook to route mail to spam, and rates above 8.0% trigger automated circuit breakers to protect sender domain reputation.

How does Photon Console automate hard bounce suppression?

When a 5xx hard bounce is received from a receiving MTA, Photon Console instantly writes the recipient address to your global suppression list in database memory, immediately blocking any future sends to that recipient and firing a bounce webhook event to your backend.

Eliminate Bounce Penalties with Automated Circuit Breakers

Deploy Photon Console's intelligent suppression engine. Automatically quarantine dirty lists, retry soft bounces gracefully, and keep domain bounce rates below 1%.