Email & OutreachUpdated Nov 13, 2026

Hard Bounce vs Soft Bounce

A hard bounce is a permanent delivery failure: the receiving server says the message will not be delivered as sent, usually because the address doesn't exist, and SMTP marks it with a 5xx code. A soft bounce is a temporary failure, such as a full mailbox or a busy server, marked with a 4xx code, and the message can be retried.

Related search hard bounce vs soft bouncesoft bounce vs hard bouncedifference between hard and soft bounce

What is the difference between a hard bounce and a soft bounce?

A hard bounce is a permanent delivery failure. The receiving mail server says the message will not be delivered as sent, usually because the address doesn’t exist or the domain has no mail server. A soft bounce is a temporary failure. The address exists, but something got in the way this time: a full mailbox, a server that’s down or overloaded, or a message that’s too large.

The difference comes straight from SMTP, the protocol mail servers use to talk to each other. RFC 5321 splits failure replies into two classes:

  • 4yz, “Transient Negative Completion reply.” “The error condition is temporary, and the action may be requested again.” This is a soft bounce.
  • 5yz, “Permanent Negative Completion reply.” The client “SHOULD NOT repeat the exact request.” This is a hard bounce.

The RFC’s own rule of thumb: a reply is temporary if the same command could succeed if repeated “without any change in command form or in properties of the sender or receiver.” If something has to change (the address, the message, your setup), it’s permanent.

For how bounces add up to a campaign metric and what a healthy rate looks like, see email bounce rate.

Hard bounce vs soft bounce at a glance

Hard bounceSoft bounce
Type of failurePermanentTemporary
SMTP reply class5xx4xx
Enhanced status class (RFC 3463)5.x.x, “Permanent Failure”4.x.x, “Persistent Transient Failure”
Common causesAddress doesn’t exist, domain doesn’t exist, permanent blockMailbox full, server busy or down, message too large, rate limits
Will a retry work?Not without a changeOften, later
What your email tool doesSuppresses the address from future sendsRetries, then counts it; repeated soft bounces become hard
What you should doRemove or fix the address; never resend as isWait; remove after repeated soft bounces

Which SMTP codes mean hard and soft bounces?

Bounce messages usually carry two codes: a three-digit SMTP reply from RFC 5321 and an enhanced status code (like 5.1.1) from RFC 3463. The enhanced code tells you the reason more precisely.

CodeDefined asBounce typeWhat to do
550 / 5.1.1Mailbox unavailable / “Bad destination mailbox address”HardAddress is wrong or gone. Remove it
5.1.2”Bad destination system address”HardDomain is wrong or has no mail server. Remove it
553”Mailbox name not allowed (e.g., mailbox syntax incorrect)“HardFix the address format
5.7.1”Delivery not authorized, message refused”Hard, but often policyCheck authentication and reputation before removing the contact
552 / 5.2.2”Exceeded storage allocation” / “Mailbox full”Varies (see below)Retry later; remove if it repeats
450”Mailbox unavailable (e.g., mailbox busy or temporarily blocked for policy reasons)“SoftRetry later
451”Requested action aborted: error in processing”SoftRetry later
452”Insufficient system storage”SoftRetry later
4.4.7”Delivery time expired”Soft that ran out of retriesCheck the address and send again later

Code definitions are quoted from RFC 5321 section 4.2 and RFC 3463 section 3. Mail servers add their own text after the code, so read the whole line.

Two caveats from the standards themselves. RFC 5321 notes that “even some ‘permanent’ error conditions can be corrected,” for example after a spelling fix or an account change. And RFC 3463 says a disabled mailbox (X.2.1) can be “a permanent error if the mailbox will never be re-enabled or a transient error if the mailbox is only temporarily disabled.” The code is a strong hint, not a verdict.

Why do email tools disagree on hard vs soft bounces?

Because each tool sorts bounces with its own rules on top of the codes. A full mailbox is the clearest case:

SourceHow it treats a full mailboxOther rules
RFC 3463 (X.2.2)“Should be used as a persistent transient failure”, so soft
MailchimpSoft bounce (“Mailbox is full (over limit)“)Converts to hard after 7 soft bounces with no subscriber activity, up to 15 with past activity
HubSpotHard bounce (“Mailbox full: an inbox that is inactive or has exceeded its storage quota for a long time”)Retries pending bounces for up to 72 hours before calling them soft; an address that hard bounces across three or more HubSpot accounts is a “global bounce” dropped everywhere

HubSpot also files content, spam and policy rejections under hard bounces, and says a hard bounce “can also be caused by a strict email security filter.” Mailchimp lists content blocks, DMARC failures and policy rejections under soft bounces. So the same rejected email can count as hard in one tool and soft in another. If your bounce numbers jump after switching tools, compare the reasons before you blame the list.

How should you handle each type?

Hard bounces

  1. Read the reason. “Unknown user” or 5.1.1 means the address is bad: remove it.
  2. If the reason is policy, spam or authentication (often 5.7.x), the address may be fine and the problem is your sending setup. Check SPF, DKIM and DMARC and your sender reputation before deleting good contacts.
  3. Never send to a hard-bounced address again without fixing it. Most email tools suppress it for you; make sure the suppression syncs to every tool that sends.

Soft bounces

  1. Let your tool retry. RFC 5321 says senders should wait at least 30 minutes between retries and keep trying for “at least 4-5 days” before giving up.
  2. Track repeat offenders. Google’s sender guidelines suggest you “automatically unsubscribe recipients who have multiple bounced messages.”
  3. If many addresses at different domains soft bounce at once, look at your side: volume spikes, a large message or a reputation problem.

Hard and soft bounces in cold email

Cold outreach has less room for error than a newsletter, because you have no engagement history to offset bounces. Three rules:

  • Verify before the first send. Most hard bounces in cold email come from addresses that were never valid or have gone stale. Verification removes them before they cost you.
  • Treat catch-all results as unknown. A catch-all domain accepts every address during verification and may reject the message later as a hard bounce.
  • Stop sooner on soft bounces. Two or three soft bounces in a row to the same contact is enough to pause. A newsletter tool’s limit of 7 or 15 is built for subscribers, not prospects.

For the full routine of removing bounces, complaints and inactive contacts, see list hygiene.

Common questions about Hard Bounce vs Soft Bounce

What is the difference between a hard bounce and a soft bounce?

A hard bounce is permanent: the receiving server says the message can't be delivered as sent, most often because the address doesn't exist. A soft bounce is temporary: the mailbox is full, the server is busy or the message is too large, and a retry may work. In SMTP, permanent failures use 5xx reply codes and temporary ones use 4xx codes (RFC 5321).

Should I remove soft bounces from my email list?

Not after one. Remove an address after repeated soft bounces. Mailchimp converts a soft bounce to a hard bounce after 7 soft bounces for contacts with no activity, or up to 15 for contacts with past activity. Google's sender guidelines suggest automatically unsubscribing recipients who have multiple bounced messages. For cold email, use a lower limit: two or three soft bounces in a row is enough to stop.

If an email bounces for one recipient, do the others still receive it?

Yes. A bounce is about one recipient's address or server. HubSpot's help page says an email sent to several recipients 'may bounce for some contacts and be delivered for others.' Only the failed recipients get the bounce; everyone else's copy is delivered normally.

Is a full mailbox a hard bounce or a soft bounce?

It depends on who's counting. RFC 3463 says a full mailbox (status code X.2.2) 'should be used as a persistent transient failure', which makes it a soft bounce, and Mailchimp lists 'Mailbox is full' under soft bounces. HubSpot treats 'Mailbox full' as a hard bounce when an inbox has been inactive or over quota for a long time. Read the bounce code as well as the label.

How do I fix a bounced email?

Read the bounce message first. For a hard bounce on an unknown address, check for a typo, then remove the contact if the address is wrong. For a soft bounce, wait and retry later. If the bounce mentions policy, authentication or spam, the problem is on your side: check SPF, DKIM and DMARC, and ask the recipient's IT team to allow your sending IPs if needed.

What bounce rate is too high?

Treat anything above 2% on a send as a problem to fix before the next campaign. That is a working threshold, not a published mailbox-provider limit: Google publishes a spam-rate threshold (below 0.3% in Postmaster Tools) but no bounce-rate number. Hard bounces are the ones to drive toward zero, by verifying lists before sending.

Start with one process.

We learn the business and build your first go-to-market process on us this month.