Hard Bounce
A hard bounce is a permanent email delivery failure: the receiving server has decided the message can never be delivered and rejects it outright, signalling this with a 5xx SMTP reply. The usual cause is an address that does not exist, but a block on policy or reputation grounds counts too. Unlike a soft bounce, retrying will not help, so the address must be suppressed at once.
- Permanent failure: the message will never be delivered, no matter how many retries
- Most often the recipient address does not exist or the domain has no mail server
- Remove every hard-bounced address immediately to protect your reputation
- A rising hard-bounce rate is a direct signal of poor list hygiene
5xx (e.g. 550, 554)
What a hard bounce actually is
Every SMTP transaction ends with a three-digit reply code. Codes in the 4xx range mean a transient failure, or soft bounce: try again later. Codes in the 5xx range mean a permanent failure, or hard bounce: the server is saying “never,” not “not right now.” Many receivers pair the basic code with an enhanced status code from RFC 3463, so 550 5.1.1 tells you the failure is permanent (the leading 5) and that the mailbox does not exist (.1.1).
When your mail transfer agent receives a 5xx response it does not queue the message or schedule a retry, because retrying a permanent failure is pointless. Instead it generates a non-delivery report back to the sender and drops the message. A well-behaved sending platform reads that bounce, matches it to the address, and adds it to a suppression list so the same dead address is never mailed again.
Common causes, and what each 5xx code means
A hard bounce usually arrives with a reply code that explains the permanent rejection:
550 5.1.1: the mailbox does not exist (a mistyped, fake, or long-deleted address). This is by far the most common hard bounce.550 5.1.2: the recipient domain itself is invalid or has no mail server.554 5.7.1: the message was blocked on policy grounds, often a reputation or blacklist issue rather than a bad address.553: the recipient address is malformed or rejected as invalid.
The underlying reasons cluster into a few buckets: the address was never real (typos at signup, fake entries, scraped lists), the address used to be real but has been deleted, the whole domain has no working mail server, or the receiver is permanently refusing your mail because your IP or domain reputation has collapsed. The first three are list problems; the last is a reputation problem.
Hard bounces and your sender reputation
Hard bounces hurt far more than the lost message. Every permanent failure tells a mailbox provider that you mailed an address you should not have, which is exactly the behaviour of a sender working from a stale or purchased list. A high hard-bounce rate is one of the clearest signals of poor list hygiene, and it drags down both your IP and domain reputation, which in turn pushes your good mail toward the spam folder.
Worse, some of the addresses that hard-bounce as “user unknown” today were once real mailboxes that have since been abandoned, and a share of those get reborn as recycled spam traps. Continuing to mail addresses that bounce is how senders walk straight into a trap. The fix is simple and non-negotiable: suppress every hard-bounced address on the first failure, and keep your overall bounce rate low through verification and regular cleaning.
How to handle hard bounces
- Suppress on the first bounce. A 5xx is final. Add the address to your suppression list immediately; never give it a second send.
- Verify before you send. Validating addresses at signup and before a big campaign catches typos and dead mailboxes before they ever bounce.
- Distinguish address bounces from blocks. A
554 5.7.1policy block is a reputation problem to investigate, not an address to delete. Treat the two causes differently.
How a hard bounce plays out
5xx replyHard bounce vs soft bounce
| Hard bounce | Soft bounce | |
|---|---|---|
| Duration | Permanent | Temporary |
| SMTP code | 5xx |
4xx |
| What to do | Suppress at once | Let it retry |
| Typical cause | Address does not exist | Mailbox full, throttling |
| Recoverable? | No | Often |
| Reputation impact | High, remove at once | Low if occasional |
By the numbers
Common mistakes
554 5.7.1 block means the receiver rejected your mail on reputation or blacklist grounds, not that the address is invalid. Deleting the recipient hides a reputation problem you actually need to fix.Frequently asked questions
5xx SMTP code, usually because the address does not exist or the mail is blocked on policy grounds; retrying will not help, so you suppress the address immediately. A soft bounce is a temporary 4xx failure, such as a full mailbox or a server that is briefly down, which your mail server retries automatically and often delivers on a later attempt.554 5.7.1 response), which points to a reputation issue with the receiver rather than a bad address, and should be investigated rather than simply deleted.