Hard bounce vs soft bounce
A hard bounce is a permanent delivery failure: the address doesn't exist or will never accept your mail, so remove it. A soft bounce is temporary, such as a full mailbox or a busy server, so the message is retried and the address stays on your list unless it keeps soft-bouncing.
By MailVet team
Hard vs soft bounce at a glance
| Hard bounce | Soft bounce | |
|---|---|---|
| What it means | Permanent failure: mail to this address won't be delivered | Temporary failure: delivery may work later |
| SMTP reply code | 5xx, most often 550, also 551 to 554 | 4xx, such as 421, 450, 451 and 452 |
| Enhanced status code | 5.x.x, for example 5.1.1 | 4.x.x, for example 4.2.2 |
| Typical causes | Mailbox or domain doesn't exist, mailbox disabled | Mailbox full, server busy or offline, greylisting, rate limiting |
| Retried? | No | Yes, by the sending server, for hours or days |
| What email platforms usually do | Suppress the address after the first one | Keep sending; suppress after several in a row |
| What you should do | Remove it or mark it bounced; don't re-import it | Let retries run; re-verify addresses that keep soft-bouncing |
How to tell which one you have
Look at the first digit of the code in the bounce message: 5 is permanent, 4 is temporary, and the enhanced status code (like 5.1.1) follows the same rule. If there's no code, the wording usually gives it away: "user unknown" and "no such user" are hard; "try again later" is soft.
Two cases trip people up. First, not every 5xx is a bad address. A 550 5.7.1 means the server refused your message for policy reasons, such as your IP's reputation or a failed authentication check. The address may be fine. These are often called block bounces, and deleting the address doesn't fix them. Second, a soft bounce can become final: when the sending server stops retrying, you get a delivery report with a code like 4.4.7 (delivery time expired).
Full mailboxes sit on the border. Servers report them as 4.2.2 or 5.2.2, so the same problem can be filed as hard by one tool and soft by another.
Common bounce codes, sorted
| Code | Type | Meaning | What to do |
|---|---|---|---|
| 550 5.1.1 | Hard | Mailbox doesn't exist | Remove |
| 550 5.1.2 | Hard | Domain doesn't exist or can't receive mail | Fix the typo or remove |
| 553 5.1.3 | Hard | Malformed address | Fix or remove |
| 550 5.2.1 | Hard | Mailbox disabled | Remove |
| 552 5.2.2 | Hard, but some tools file it as soft | Mailbox full | Hold; re-verify before the next send |
| 550 5.7.1 | Block | Refused by policy: reputation, blocklist or content | Fix the cause; keep the address |
| 550 5.7.26 | Block | Failed authentication (DMARC) | Fix SPF, DKIM and DMARC alignment |
| 452 4.2.2 | Soft | Mailbox full | Retried automatically |
| 421 4.7.0 | Soft | Deferred for policy reasons, often rate limiting | Slow down |
| 450 / 451 4.7.1 | Soft | Greylisted or temporarily refused | Retried automatically |
| 4.4.7 | Soft that became final | Delivery time expired after retries | Check the domain; verify the address |
What email platforms usually do with bounces
Most email service providers and cold email tools keep a suppression list. A hard bounce puts the address on it straight away, and the tool won't send to it again, usually even if you import it again. Soft bounces are retried, and an address that soft-bounces several times in a row is eventually suppressed too. The number of strikes differs from tool to tool, so check your platform's documentation.
Tools also differ on block bounces. A 5.7.x refusal says more about the sender than the address, so not every tool suppresses the address for it. Whatever yours does, a run of block bounces is a deliverability problem to fix, not a list problem.
What to do with each kind
Remove it, and remember it
Suppress the address in your sending tool and mark it bounced in your CRM. Deleting it outright means the next export or enrichment run can bring it straight back.
Let it retry, then re-check
One soft bounce is normal. If the same address soft-bounces across several campaigns, treat it as dead or re-verify it before sending again.
Fix the sender, keep the address
A 5.7.x bounce points at your authentication, IP or content. Check SPF, DKIM and DMARC, look up any blocklist named in the bounce, and slow down.
Look for a pattern
A wave of soft bounces from one provider at the same moment usually means you're being rate limited or filtered, not that hundreds of mailboxes filled up overnight.
Prevent hard bounces before you send
Most hard bounces come from addresses a verifier would have flagged. Here's how MailVet's results line up with the bounce you'd otherwise get.
| MailVet result | Reason | What sending would do |
|---|---|---|
| undeliverable | mailbox_not_found | Hard bounce, usually 5.1.1 |
| undeliverable | invalid_domain | Hard bounce (5.1.2 or 5.4.4), or no delivery attempt at all |
| undeliverable | catch_all_no_mailbox | Accepted by the server, then bounced later or lost |
| risky | mailbox_full | Soft bounce (4.2.2) or 5.2.2 |
| unknown | no_response | Can't tell yet; re-run before sending (free) |
| deliverable | accepted or catch_all_verified | Accepted, unless your message is refused for policy reasons |
Verification can't predict policy bounces (5.7.x): those depend on how your message and sending setup look to the receiver. Every reason code is explained on /email-verification-statuses.
Bounce type questions
Should I remove soft-bounced emails from my list?
Not after a single soft bounce; the sending server retries, and many retries succeed. If an address soft-bounces across several campaigns, suppress it or re-verify it before you send again.
Is a 550 error always a hard bounce?
550 is a permanent failure, but it isn't always about the address. 550 5.1.1 means the mailbox doesn't exist; 550 5.7.1 means the server refused your message for policy reasons, and the address may be valid. Read the enhanced code and the text.
How long are soft bounces retried?
It depends on the sending server. Retries usually continue for hours to a few days; Postfix, for example, keeps a message in its queue for five days by default before giving up.
Do soft bounces hurt sender reputation?
Less than hard bounces, and occasional ones are normal. Lots of them at once, or the same addresses soft-bouncing for weeks, point to a list or sending problem worth fixing.
How do I prevent hard bounces?
Verify addresses before you send: in real time for new signups, and in bulk before campaigns. Most hard bounces come from mailboxes and domains that no longer exist, which is exactly what verification detects.
Catch hard bounces before they happen
Upload a list and see which addresses would bounce, catch-alls included. 100 free credits, and unknown results are never charged.
Related
Last updated November 13, 2026