Soft Bounce Patterns and What They Mean
Not all soft bounces are the same, and treating them identically is a mistake. A soft bounce caused by a temporarily full mailbox has completely different implications than one caused by rate limiting or content-based rejection. Understanding the patterns helps you diagnose the real problem and take the right corrective action.
Pattern 1: Mailbox Full (452 or 550 with storage message)
A "mailbox full" bounce can be temporary or effectively permanent. For personal accounts, it is usually temporary. The person clears out some emails, and your next attempt delivers. For corporate accounts, a full mailbox often indicates an abandoned account. The person left the company, the mailbox filled up, and nobody is maintaining it.
How to handle it: retry twice over 48 hours. If it still bounces, suppress the address. For corporate addresses, a persistent mailbox-full error is effectively a hard bounce masquerading as a soft bounce. Do not keep retrying indefinitely.
Pattern 2: Rate Limiting (421 or 450 with throttling message)
Rate limiting means you are sending too many emails too quickly to a particular domain. The receiving server is telling you to slow down. This is not a data quality issue. It is a sending speed issue.
How to handle it: reduce your sending speed to that domain. Most ESPs allow per-domain throttling settings. Spread your sends across a longer time window. If you are sending from multiple IPs, distribute the load. Rate limiting resolves itself once you reduce the send rate.
Pattern 3: Content-Based Rejection (550 or 554 with content/policy message)
Some servers reject emails based on content analysis. This is not about the recipient address. It is about what your email contains. Common triggers include: URLs pointing to newly registered domains, specific keywords associated with spam, excessive HTML or images, and tracking pixels from known tracking services.
How to handle it: review the specific rejection message for clues about what triggered the filter. Send a plain-text test to see if content is the issue. Remove or replace flagged elements. This is not a verification problem; it is a content problem.
Pattern 4: Graylisting (451 with "try again later" message)
Graylisting is an anti-spam technique where the server intentionally rejects the first delivery attempt from an unknown sender. Legitimate mail servers retry. Spam bots usually do not. After the retry, the email delivers normally and future emails from your server are accepted without delay.
How to handle it: nothing. Your ESP should retry automatically. If you are seeing graylisting bounces in your reports, it means your ESP is logging the initial rejection before the retry succeeds. Check whether the retried attempt delivered. If it did, ignore the initial gray list bounce in your metrics.
Pattern 5: Server Temporarily Unavailable (421 without specific reason)
The receiving mail server is down for maintenance or experiencing an outage. This affects all emails to that domain, not just yours. Usually resolves within hours.
How to handle it: retry in 1-4 hours. If the issue persists for more than 24 hours, the server may have a more serious problem. Check if the domain's MX records are still valid. If the server has been down for days, the company may have had an infrastructure issue or migration.
Pattern 6: Connection Timeout (no response)
Your sending server could not establish a connection to the receiving server at all. No SMTP response was received. This could be a DNS issue, a network routing problem, or a receiving server that is completely offline.
How to handle it: check the domain's MX records. If they exist and point to valid servers, retry in a few hours. If MX records are missing or point to non-responsive servers, treat as a potential permanent failure. The domain may have lost its email infrastructure.
Tracking Patterns Over Time
Individual soft bounces are not concerning. Patterns of soft bounces are. Track soft bounces per domain over time. If the same domain soft bounces on every campaign for three consecutive sends, something systemic is happening. Investigate the domain specifically.
Also track soft bounce patterns by sending time. If bounces spike during your first hour of sending and then decrease, you are likely hitting rate limits. Spread your sends more evenly.
For catch-all domains that soft bounce, the diagnosis is more complex. The server might accept the email (no bounce) but the mailbox might not exist (nobody reads it). Standard soft bounce analysis does not detect this. CatchallVerifier resolves this by verifying actual mailbox deliverability before you send, preventing the silent failures that do not produce bounces but still waste your sending resources.
The bottom line: soft bounces are your email infrastructure talking to you. Listen to what each pattern is saying, and you will catch problems while they are still fixable.
