## Why Hard Bounces Deserve Their Own Playbook Every bulk email send produces some bounces. Most teams look at a single bounce rate, notice when it climbs, and move on. But a bounce is not just a number. Each one comes with a response from the receiving mail server that says why the message was refused, and those responses tell you very different things about your list.
Some hard bounces mean an address will never work again. Others mean the domain itself is gone. A few look permanent but actually point to a problem on your side, such as a failed authentication check or a block on your sending reputation. If you treat all of them the same way, you either keep mailing dead addresses or you suppress good subscribers because of a problem you could have fixed.
This guide explains how to read hard bounce codes, which SMTP responses mean an address should be suppressed for good, which ones should not be treated as list problems at all, and how to build a simple, consistent process around them. It also covers how hard bounces connect to validation, list imports, and long-term list health. ## Hard Bounces vs Soft Bounces in One Paragraph A soft bounce is a temporary failure.
The mailbox may be full, the server may be busy, or the receiver may be slowing you down. The message might be delivered if it is retried later, and a single soft bounce is not a reason to remove anyone. A hard bounce is a permanent failure.
The receiving server has told you, in effect, "do not try this again." Repeating the same send to the same address will produce the same result and will slowly damage your sender reputation. If you want the detailed playbook for temporary failures, see our soft bounce playbook. This post focuses on the permanent side.
## How to Read an SMTP Bounce Response When a receiving server rejects a message, it returns a response that usually has three parts: - **A basic reply code**, such as `550` or `554`. Codes that start with 5 are permanent failures. Codes that start with 4 are temporary. - **An enhanced status code**, such as `5.1.1`. This more specific code follows the format class.subject.detail.
The first digit repeats the class (5 for permanent, 4 for temporary). The second digit says what kind of problem it is: addressing, mailbox, mail system, network and routing, protocol, content, or security and policy. - **A text description**, written by the receiving server. It might say "user unknown," "mailbox disabled," or something more detailed with a link to the receiver's help page.
A typical hard bounce looks like this: `550 5.1.1 The email account that you tried to reach does not exist.` The basic code tells you it is permanent. The enhanced code tells you it is an addressing problem with the recipient. The text confirms what happened in plain language. ### Read the enhanced code first The basic reply code is too broad to act on by itself.
A `550` can mean the mailbox does not exist, but receivers also use it for policy blocks and spam rejections. The enhanced code is much more useful, and the text description fills in the rest. When the enhanced code and the text disagree, trust the text, because receivers do not always pick the most precise code.
### Your provider may normalize the response When you send through an email service provider, you usually do not see the raw SMTP conversation. The provider receives the bounce, classifies it, and passes it back to you as an event or a status, often with the original response attached. Different providers label these events differently.
One may call a message "bounced," another "failed," another "rejected" or "dropped." Before you build rules, check how your provider reports permanent failures, and whether it keeps its own suppression list that silently skips addresses which hard bounced before. ## The Subject Groups That Matter Most The middle digit of the enhanced code is the quickest way to sort hard bounces into buckets. Here are the groups you will see most often.
### X.1.X: Addressing problems These codes say something is wrong with the address itself. - **5.1.1 (bad destination mailbox address):** The mailbox does not exist at that domain. This is the classic hard bounce. Usually the result of a typo, an employee who left a company, an abandoned account, or a made-up address entered on a form. - **5.1.2 (bad destination system address):** The domain part of the address is wrong or cannot receive mail.
Often a typo in the domain, such as a misspelled popular mailbox provider, or a domain that has expired. - **5.1.3 (bad destination mailbox address syntax):** The address is not valid. In a healthy pipeline this should almost never reach the send stage, because syntax checks at capture or import should catch it.
- **5.1.10 (recipient address has null MX):** The domain publishes a "null MX" record, which is an explicit statement that it does not accept email at all. Addressing bounces are the clearest case for permanent suppression. The address is not going to start working because you tried again next week. ### X.2.X: Mailbox status problems These codes say the address exists but the mailbox cannot accept mail.
- **5.2.1 (mailbox disabled, not accepting messages):** The account has been disabled or closed. Many large mailbox providers return this for accounts that have been inactive for a long time. - **5.2.2 (mailbox full):** The mailbox is over its storage quota. Even though the class digit is 5, many senders treat this as a soft bounce, because the person might clear space.
If the same address keeps returning "mailbox full" across several sends over weeks, the mailbox is most likely abandoned and should be suppressed. - **5.2.3 (message length exceeds administrative limit):** Your message is too large for that mailbox. This is a problem with the message, not the subscriber. Disabled mailboxes are a strong suppression signal. Full mailboxes are a pattern to watch, not a one-strike rule.
### X.4.X: Network and routing problems - **5.4.1 or 5.4.4 (no answer from host, unable to route):** The domain has no working mail servers, or mail cannot be routed to them. If the domain is gone, the address is effectively dead. If the domain has a short outage or a broken DNS change, it may come back. Treat routing failures carefully.
A single routing failure for one address on a big, well-known domain is unusual and worth a second look. Routing failures for a small company domain that has lapsed are usually permanent. ### X.7.X: Security and policy problems This is where most mistakes happen. Codes in this group often look like hard bounces, but they usually describe your sending, not the recipient's address. - **5.7.1 (delivery not authorized, message refused):** A broad policy rejection.
It can mean the recipient's server is blocking your sending IP or domain, that the content tripped a filter, or that the recipient has set rules that block you. - **5.7.26 and similar authentication failures:** The receiver rejected the message because it failed authentication checks such as SPF, DKIM, or DMARC alignment. The text usually mentions authentication or links to the receiver's sender guidelines.
- **Blocklist references:** The text mentions a blocklist, a reputation system, or "poor reputation." The problem is your sending IP or domain. If you suppress addresses because of policy bounces, you can wipe out large numbers of real, engaged subscribers at a single mailbox provider during a reputation dip or an authentication mistake. Policy bounces should trigger an investigation into your sending setup, not automatic list removal.
### X.3.X, X.5.X, and X.6.X: System, protocol, and content problems These groups cover issues such as a server that cannot handle a feature, a protocol error during the SMTP conversation, or content the receiver will not accept. They are rarely about the recipient's address. Log them, look for patterns by provider and campaign, and fix the cause.
## A Practical Classification Table When you set rules, it helps to map each type of hard bounce to an action and an owner.
| Bounce type | Typical codes | What it means | Action | Owner | |---|---|---|---|---| | Mailbox does not exist | 5.1.1 | Address is dead | Suppress permanently | List hygiene | | Bad or dead domain | 5.1.2, 5.1.10, some 5.4.4 | Domain cannot receive mail | Suppress permanently | List hygiene | | Invalid syntax | 5.1.3 | Address is malformed | Suppress and fix capture | List hygiene and forms
| | Mailbox disabled | 5.2.1 | Account closed or dormant | Suppress permanently | List hygiene | | Mailbox full (repeated) | 5.2.2 | Likely abandoned | Suppress after repeated failures | List hygiene | | Message too large | 5.2.3, 5.3.4 | Your message is too big | Fix the template | Content | | Policy or reputation block | 5.7.1, blocklist text | Receiver distrusts your sending | Investigate sending, do not
suppress | Deliverability | | Authentication failure | 5.7.26 and similar | SPF, DKIM, or DMARC problem | Fix authentication,
Related Articles
A practical 2026 guide to GDPR and CAN-SPAM compliance for email marketers, covering consent, data handling, unsubscribe rules, and campaign-safe automation.
Discover actionable strategies to boost your sms open rates, enhance text message engagement, and maximize ROI in your sms marketing campaigns.
Discover the true financial drain of poor data quality and how strategic list hygiene practices in 2026 can transform your marketing, boost efficiency, and deliver substantial ROI.
A missing country code or a leftover trunk zero can turn a real subscriber into a failed text or a wrong-country charge. Learn how E.164 works, why local formats break bulk SMS
Double opt-in filters out typos, bots, and signups in someone else's name. Learn when to use it for email and SMS and how to keep real signups.
A list that was clean last quarter is not clean today. Learn why email lists decay, how to set a re-validation cadence by segment, which addresses to check first, and how to act on
Messy contact files cause bounces, failed texts, and duplicate messages. Learn how to map, normalize, dedupe, and validate imports before you send.
Discover the critical differences between real-time and batch email validation, their benefits, and how to integrate both for optimal email list hygiene and deliverability in 2026.
Explore SESender
SESender brings audience preparation, contact validation, sender and provider controls, scheduling, delivery tracking, and campaign reporting into one workspace. Review the current product and pricing information before deciding whether the platform fits your messaging workflow.
Explore the platform or review pricing.