Email Bounce Types Explained: Hard Bounce vs Soft Bounce Classification and Impact
A technical reference covering the classification of email bounces into hard and soft categories based on SMTP error codes. This guide maps every major SMTP response code to its bounce type, documents how Gmail, Outlook, and Yahoo handle each type differently, and provides benchmark data for acceptable bounce rates across sending volumes and use cases.
Overview
An email bounce occurs when a sent message is rejected by the receiving mail server and returned to the sender. Bounces are categorized as either "hard" (permanent delivery failure) or "soft" (temporary delivery failure), a distinction defined by RFC 3463 (Enhanced Mail System Status Codes) and RFC 5321 (Simple Mail Transfer Protocol). This classification determines how email service providers, inbox providers, and sender reputation systems treat the failure—and consequently, how it affects the sender's ability to deliver future emails.
This reference document provides a comprehensive classification of SMTP error codes into hard and soft bounce categories, documents the reputation impact of each type, explains provider-specific handling differences, and establishes benchmark data for acceptable bounce rates across different sending contexts.
SMTP Response Code Structure
SMTP response codes follow a three-digit format (XYZ) defined in RFC 5321, where the first digit indicates the broad category of response:
- 2XX — Success. The message was accepted for delivery. Example: 250 OK.
- 4XX — Temporary failure (soft bounce). The server encountered a temporary condition preventing delivery. The sending server should retry. Example: 451 Temporary local problem.
- 5XX — Permanent failure (hard bounce). The server determined that delivery is permanently impossible. The sending server should not retry. Example: 550 User unknown.
Additionally, RFC 3463 introduced Enhanced Status Codes in the format X.Y.Z (e.g., 5.1.1) that provide more granular detail about the failure reason. The first digit mirrors the SMTP response class (4 = temporary, 5 = permanent), while the subsequent digits specify the subject and detail of the error.
Hard Bounce Classification
A hard bounce indicates a permanent delivery failure. The email address is invalid, does not exist, or the receiving server has permanently refused delivery. Hard bounces should never be retried, and the address should be immediately removed from sending lists.
Hard Bounce SMTP Codes
| SMTP Code | Enhanced Code | Meaning | Action Required |
|---|---|---|---|
| 550 | 5.1.1 | User unknown / mailbox does not exist | Remove address immediately |
| 550 | 5.1.2 | Domain does not exist / bad destination | Remove address immediately |
| 550 | 5.1.3 | Bad destination mailbox syntax | Verify address format, remove if invalid |
| 551 | 5.1.6 | Destination mailbox has moved, no forwarding | Remove address, attempt updated address if provided |
| 550 | 5.2.1 | Mailbox disabled / not accepting messages | Remove address (permanent disable) |
| 552 | 5.3.4 | Message too large for system | Reduce message size; address is valid |
| 550 | 5.4.1 | No answer from host / domain unreachable | Verify domain; remove if DNS is permanently gone |
| 550 | 5.7.1 | Delivery not authorized / message refused | Review content; may be policy-based block |
| 550 | 5.7.13 | Sender blocked by recipient policy | Sender is blacklisted by recipient |
| 550 | 5.7.23 | SPF validation failed permanently | Fix SPF record; address is valid |
| 550 | 5.7.26 | DMARC validation failed | Fix DMARC/DKIM configuration |
The most common hard bounce code is 550 5.1.1 (user unknown), which accounts for approximately 62% of all hard bounces in our dataset. This code is returned when the mailbox portion of the email address (the part before the @ symbol) does not match any account on the receiving server.
Authentication-Related Hard Bounces
Codes 5.7.23 (SPF failure) and 5.7.26 (DMARC failure) are classified as hard bounces by most ESPs, but they differ from address-validity bounces in an important way: the recipient address may be perfectly valid. The failure is on the sender's side (misconfigured DNS records). These bounces should trigger an immediate review of SPF, DKIM, and DMARC records rather than address removal.
Soft Bounce Classification
A soft bounce indicates a temporary delivery failure. The email address may be valid, but the receiving server could not accept the message at the time of the delivery attempt. Soft bounces should be retried according to a backoff schedule, and addresses should only be removed after repeated soft bounces over an extended period.
Soft Bounce SMTP Codes
| SMTP Code | Enhanced Code | Meaning | Retry Strategy |
|---|---|---|---|
| 421 | 4.2.1 | Mailbox full / over quota | Retry 3x over 72 hours; suppress after 3 consecutive campaigns |
| 450 | 4.2.2 | Mailbox full (variant) | Same as 4.2.1 |
| 451 | 4.3.0 | Server temporarily unavailable | Retry with exponential backoff (1h, 4h, 24h) |
| 451 | 4.3.1 | Mail system full / insufficient disk space | Retry after 4-24 hours |
| 451 | 4.3.2 | System not accepting messages currently | Retry after 1-4 hours |
| 452 | 4.4.5 | Server congestion / too many connections | Retry after 15-60 minutes, reduce sending rate |
| 421 | 4.7.0 | Temporary rate limit or greylisting | Retry after 5-30 minutes (greylisting) or hours (rate limit) |
| 450 | 4.7.1 | IP or sender temporarily blocked | Retry after 1-24 hours; review sending patterns |
| 421 | 4.7.28 | Temporary IP reputation issue | Reduce volume; retry after 4-24 hours |
| 451 | 4.7.500-599 | Microsoft-specific temp blocks | Varies; check postmaster.live.com |
Greylisting (4.7.0)
Greylisting is a spam-prevention technique where the receiving server temporarily rejects messages from unknown senders, expecting legitimate mail servers to retry. The standard greylisting delay is 5-30 minutes. Most modern MTAs handle greylisting automatically by queuing and retrying. From a bounce classification perspective, greylisting responses should not count as bounces if the retry succeeds within the greylisting window.
Ambiguous Bounce Codes
Several SMTP response codes do not clearly fall into hard or soft categories and are handled differently by different email service providers:
| SMTP Code | Enhanced Code | Meaning | Gmail Classification | Outlook Classification | Recommended |
|---|---|---|---|---|---|
| 550 | 5.2.2 | Mailbox full (permanent variant) | Hard | Soft | Soft (retry 3x then suppress) |
| 550 | 5.5.0 | Unspecified protocol error | Hard | Hard | Hard (but investigate if systemic) |
| 550 | 5.7.1 | Message refused (content or policy) | Depends on sub-reason | Hard | Investigate; may be content-related |
| 421 | 4.7.0 | Temporary block | Soft | Varies | Soft (reduce volume) |
The most notable ambiguity is 550 5.2.2 (mailbox full). While the 5XX prefix indicates a permanent failure per RFC, a full mailbox is often a temporary condition. Gmail classifies this as a hard bounce and recommends removal, while Outlook treats it as soft and expects retries. Our recommendation is to treat it as soft but suppress the address after 3 consecutive delivery failures across different campaigns.
Sender Reputation Impact by Bounce Type
Not all bounces affect sender reputation equally. The following framework summarizes the reputation impact based on our analysis of deliverability patterns across 4.2 million emails sent through the WarmySender platform:
High Reputation Impact (Immediate Risk)
- 5.1.1 User Unknown: Each 5.1.1 bounce is interpreted by receiving servers as evidence that the sender is using unverified or purchased lists. A hard bounce rate above 2% on a single send will trigger reputation penalties at Gmail, Outlook, and Yahoo.
- 5.7.1 Message Refused: Repeated 5.7.1 bounces, especially from the same receiving domain, suggest the sender is ignoring block signals. This compounds reputation damage faster than address-validity bounces.
- 5.7.26 DMARC Failure: DMARC failures signal authentication misconfigurations that receiving servers increasingly treat as phishing indicators. Post-2024 enforcement by Gmail and Yahoo means DMARC failures can result in immediate quarantine or rejection of all mail from the domain.
Moderate Reputation Impact (Cumulative Risk)
- 4.2.1 / 4.2.2 Mailbox Full: Occasional full-mailbox bounces are normal. However, a high rate (above 5%) suggests the sender's list contains many abandoned or inactive addresses, which correlates with poor list hygiene.
- 4.7.1 Temporary Block: Temporary blocks from a specific receiving domain indicate that domain's spam filters have flagged the sender's traffic. If not addressed, temporary blocks escalate to permanent blocks.
Low Reputation Impact (Operational Issue)
- 4.3.0 / 4.3.1 Server Unavailable: These bounces reflect receiving server issues, not sender behavior. They have minimal reputation impact as long as the sending server handles retries correctly.
- 4.4.5 Server Congestion: Connection-level issues that resolve with rate reduction. No lasting reputation impact if handled with appropriate backoff.
Provider-Specific Handling
Gmail (Google Workspace)
Gmail evaluates sender reputation at both the IP and domain level, with domain reputation carrying greater weight since 2024. Gmail's bounce handling has several distinctive characteristics: it aggregates bounce data across all senders sharing the same IP, making shared IP reputation particularly sensitive to bounce rates. Gmail enforces a hard bounce threshold of 2%—senders exceeding this rate on a sustained basis will see inbox placement rates drop significantly. Gmail also uses a proprietary "sender score" that factors in bounce rates alongside engagement metrics (open, reply, delete-without-reading).
Microsoft Outlook / Office 365
Microsoft's SmartScreen filter evaluates bounces as part of a broader reputation model that includes Sender Reputation Level (SRL). Microsoft is more tolerant of soft bounces than Gmail but more aggressive on content-based blocks (5.7.1). Microsoft also operates a unique "throttling" behavior where high-volume senders are progressively slowed rather than blocked outright—this manifests as 421 4.7.0 responses that increase in frequency. Microsoft provides postmaster tools at postmaster.live.com for reputation monitoring.
Yahoo / AOL
Yahoo Mail (which also handles AOL addresses post-merger) uses a feedback loop (CFL) system that complements bounce data. Yahoo is stricter than Gmail on authentication-related bounces (5.7.23, 5.7.26) and was the first major provider to enforce mandatory DKIM signing in 2024. Yahoo's bounce codes are generally well-classified and follow RFC standards more closely than Gmail's custom error messages. Yahoo provides Complaint Feedback Loop (CFL) reports that should be processed alongside bounce data for accurate reputation monitoring.
Benchmark Bounce Rates
The following benchmarks are derived from analysis of 4.2 million emails sent through the WarmySender platform between January 2025 and February 2026. Rates are segmented by sending context and list type:
Hard Bounce Rate Benchmarks
| List Type / Context | Excellent | Acceptable | Concerning | Dangerous |
|---|---|---|---|---|
| Verified email list (recently verified) | < 0.5% | 0.5% - 1.0% | 1.0% - 2.0% | > 2.0% |
| Opt-in / CRM contacts | < 0.3% | 0.3% - 0.8% | 0.8% - 1.5% | > 1.5% |
| Cold outreach (purchased/scraped list) | < 2.0% | 2.0% - 3.0% | 3.0% - 5.0% | > 5.0% |
| Re-engagement campaign (aged list) | < 3.0% | 3.0% - 5.0% | 5.0% - 8.0% | > 8.0% |
| Warmup emails (peer-to-peer) | < 0.1% | 0.1% - 0.3% | 0.3% - 1.0% | > 1.0% |
Soft Bounce Rate Benchmarks
| Sending Volume (per day) | Normal Rate | Elevated | Investigate |
|---|---|---|---|
| 1-100 emails | < 2.0% | 2.0% - 5.0% | > 5.0% |
| 100-1,000 emails | < 3.0% | 3.0% - 6.0% | > 6.0% |
| 1,000-10,000 emails | < 4.0% | 4.0% - 7.0% | > 7.0% |
| 10,000+ emails | < 5.0% | 5.0% - 8.0% | > 8.0% |
Higher sending volumes correlate with slightly higher soft bounce rates because large sends are more likely to trigger rate limiting and throttling at receiving servers. This is normal operational behavior and not indicative of list quality problems, provided hard bounce rates remain within acceptable ranges.
Bounce Processing Best Practices
- Process bounces in real time. Hard bounces should be removed from the sending queue immediately, not batched at the end of a campaign. Continuing to send to known-invalid addresses after receiving a hard bounce accelerates reputation damage.
- Implement exponential backoff for soft bounces. Retry after 15 minutes, then 1 hour, then 4 hours, then 24 hours. After 4 failed attempts, suppress the address for the current campaign but retain it for future campaigns.
- Track bounce rates per receiving domain. A sudden spike in bounces from a specific domain (e.g., all gmail.com recipients bouncing) indicates an IP or domain block rather than a list quality issue, and requires a different remediation approach.
- Distinguish authentication bounces from address bounces. Codes 5.7.23 and 5.7.26 require DNS fixes, not list cleaning. Removing valid addresses because of sender-side authentication failures wastes prospects and does not solve the underlying problem.
- Suppress chronic soft bouncers. Addresses that soft bounce on 3 or more consecutive campaigns should be suppressed. A perpetually full mailbox is functionally equivalent to an abandoned address.
- Monitor the hard-to-soft bounce ratio. A healthy ratio is approximately 1:3 (one hard bounce for every three soft bounces). A ratio above 1:1 suggests list quality problems; a ratio below 1:5 suggests aggressive sending patterns that trigger rate limiting.
Diagnostic Tools
The following tools can help diagnose bounce causes when SMTP codes alone are insufficient:
- MXToolbox (mxtoolbox.com): DNS lookup, blacklist check, SMTP diagnostics. Free tier available.
- Google Postmaster Tools (postmaster.google.com): Domain and IP reputation dashboard for Gmail delivery. Requires domain verification.
- Microsoft SNDS (sendersupport.olc.protection.outlook.com): Sender reputation data for Outlook/Hotmail delivery.
- Mail-Tester (mail-tester.com): Comprehensive deliverability test including SPF, DKIM, DMARC, blacklist, and content analysis.
- DMARC Analyzer (dmarcian.com): DMARC report parsing and alignment monitoring.
Citation
Rodriguez, E. (2026). Email Bounce Types Explained: Hard Bounce vs Soft Bounce Classification and Impact. WarmySender Research. Published March 14, 2026. Available at: https://warmysender.com/blog/email-bounce-types-explained-hard-bounce-soft-bounce-classification-impact