Guides
Hard bounce and soft bounce: what they are and what to do
A bounce is an email that comes back undelivered. A hard bounce is permanent: the address doesn't exist or refuses the message for good, and it should leave your list. A soft bounce is temporary: a full mailbox or a server that's down, and delivery is usually retried. A bounce rate under 2% is healthy; above 5%, the account is at risk.
What a bounce is
A bounce is the recipient server's response saying it didn't accept the message. It comes with a code and a reason, and the sending platform uses that response to decide whether to retry or remove the address from the list.
When you send from a regular email program, the bounce shows up as a message back, usually from MAILER-DAEMON or Mail Delivery Subsystem. Inside, it carries a technical block like this:
Final-Recipient: rfc822; john@example.com
Action: failed
Status: 5.1.1
Diagnostic-Code: smtp; 550 5.1.1 The email account that you tried to reach does not exist.The Status line is what matters. The first digit gives the nature: 5 is permanent, 4 is temporary. The following digits give the reason.
| Hard bounce | Soft bounce | |
|---|---|---|
| Nature | Permanent | Temporary |
| SMTP code | Starts with 5 (e.g. 550) | Starts with 4 (e.g. 421, 452) |
| Common causes | Nonexistent address, invalid domain, permanent block | Full mailbox, server unavailable, message too large, receiving limit |
| What to do | Remove the address from the list and don't send again | Let the platform retry; if it persists, treat it as permanent |
The most common bounce codes
| Code | What it means | Type | What to do |
|---|---|---|---|
| 550 5.1.1 | The mailbox doesn't exist | Hard | Suppress the address |
| 550 5.1.2 | The destination domain doesn't exist or doesn't receive email | Hard | Suppress and look for a typo in the domain |
| 553 5.1.3 | Badly formatted address | Hard | Fix it at the signup source |
| 552 5.2.2 | Mailbox full | Soft in practice, despite the 5 | Retry; if it lasts weeks, treat as inactive |
| 421 4.7.0 | Temporary refusal, often due to volume or reputation | Soft | Slow down and let the platform retry |
| 450 4.2.1 | The recipient is receiving messages too fast | Soft | Wait |
| 451 4.3.0 | Temporary error on the destination server | Soft | Automatic retry |
| 550 5.7.1 | Policy refusal: content, reputation or blocklist | Block | Investigate the cause, don't just suppress |
| 550 5.7.26 | Gmail: message without valid authentication | Block | Fix SPF, DKIM and DMARC |
Codes vary from provider to provider, and the text after the number usually explains more than the number itself. That's why it's worth keeping the raw message of every bounce.
Block bounces: the third type
The 5.7.x codes deserve separate attention. With them, the address exists; you're the one who was refused. Typical causes are missing authentication, poor domain reputation, spammy-looking content or an IP on a blocklist. Treating this response as a hard bounce and just suppressing the contact hides the problem: the next send to the same provider will fail the same way.
Why hard bounces are dangerous
Sending to addresses that don't exist is one of the clearest signs of a poorly maintained, purchased or old list. Providers such as Gmail and Outlook start distrusting the sender, and sending infrastructure providers impose their own limits: accounts commonly go under review when the bounce rate passes 5%.
A healthy rate stays below 2%. Above that, it's worth investigating where the contacts came from before the next send.
The effect shows up outside sending platforms too. Gmail itself warns that when many of an account's messages bounce because of invalid addresses, its sending can be blocked for up to 24 hours.
How to calculate your bounce rate
The math is simple: bounces divided by messages sent, times 100. A campaign sent to 10,000 contacts with 180 bounces has a 1.8% rate. Separate hard and soft in the analysis: 1.8% soft bounces on a day a provider is unstable is very different from 1.8% nonexistent addresses.
| Rate | Reading | Action |
|---|---|---|
| Below 2% | Healthy | Keep up list hygiene |
| 2% to 5% | Warning | Find out which import or source the bounces came from |
| Above 5% | Risk to the account | Stop, clean the list and resume with recently engaged contacts |
Calculate per campaign, not just per month. A bad spreadsheet import gets diluted in the monthly average and only shows up once the damage is done.
Most common causes of mass bounces
- An old list, with no sends in over a year: former employees' addresses and domains that no longer exist.
- A purchased list or one scraped from the internet.
- Typos at signup (gmial.com, hotmal.com) with no validation on the form.
- A spreadsheet import with swapped columns.
- Business addresses at companies that changed domains or shut down.
- A form with no bot protection that signs up made-up addresses.
Soft bounces: when to stop retrying
With a soft bounce, the platform retries delivery for a few hours. If the message keeps coming back, it gives up on that send, but the contact stays on the list. The risk is the chronic soft bounce: a mailbox that has been full for months has almost always been abandoned.
A rule of thumb: the same address soft bouncing in three campaigns in a row, or bouncing for more than 30 days, should leave the active list. If you work with engagement segments, that contact should already be out of your main audience anyway.
How to reduce bounces
- Only send to people who signed up or have a relationship with your company.
- Keep a regular cadence: lists that receive email often age less.
- Validate the email format at signup and confirm the address when possible.
- Never re-import addresses that have already hard bounced.
- Before reactivating an old list, send to the most recent contacts first and watch the bounce rate.
- Record the source of every import, so you know where a problem batch came from.
What to do after a bounce spike
- Stop scheduled sends to the same list.
- Find the source: which import, form or segment concentrated the bounces.
- Separate the codes. Lots of 5.1.1 point to a bad list; lots of 5.7.x point to authentication or reputation.
- Make sure hard bounces are suppressed and don't come back in a future import.
- If there are blocks, check SPF, DKIM and DMARC and the campaign content.
- Resume with your most engaged segment at lower volume, increasing gradually.
List hygiene checklist
- Hard bounces suppressed automatically and permanently.
- Spam complaints and unsubscribes suppressed too.
- Chronic soft bounces removed from the active list.
- Contacts with no clicks for many months left out of the main send.
- Source and legal basis noted for every import.
- Bounce rate checked on every campaign, not just at month end.
How WiseData Mail handles bounces
Every hard bounce automatically goes onto the account's suppression list: the address no longer receives any campaign or automation, and a send attempt through the API comes back with the status suppressed. The raw reason reported by the provider is recorded on the contact's timeline, so you know why it wasn't delivered.
The health panel tracks the account's bounce rate, and a campaign that starts bouncing too much is paused before it hurts the domain.
A high bounce rate can also be an authentication problem. Check the SPF, DKIM and DMARC guide.
Automatic suppression, health panel and campaign pausing on every plan. See bulk email with WiseData Mail.
Frequently asked questions
Can a soft bounce become a hard bounce?
It can. If the same address bounces temporarily on consecutive sends, it's usually treated as inactive and removed from the list.
What bounce rate is acceptable?
Below 2% is healthy. Between 2% and 5% calls for a look at where the list came from. Above 5%, sending providers commonly put the account under review.
Can I send again to a contact that hard bounced?
It isn't recommended. If the address was corrected, add the correct address instead of reactivating the old one.
Is a full mailbox a hard or soft bounce?
In practice, soft. Some providers respond with code 552, which starts with 5, but the situation is temporary. If the mailbox stays full for weeks, treat the address as inactive.
Why did an address that exists bounce?
It was probably a block, with a 5.7.x code. The provider refused the message because of authentication, reputation or content, not the address. Fix the cause before resending.
Does verifying the list before sending solve it?
Verification tools help remove nonexistent addresses from an old list, but they don't fix the root cause. What reduces bounces for good is signup with consent, a regular cadence and automatic suppression.
Keep reading
SPF, DKIM and DMARC: what they are and how to set them up
The three DNS records that tell Gmail and Outlook the email really comes from you.
Read the guideHow to create an email newsletter
From goal to editorial calendar: the step-by-step for a newsletter that reaches the inbox and gets read.
Read the guideHow to send bulk email from Gmail (and when to stop)
Gmail's official limits, Bcc versus mail merge, the risks to your domain and the signs it's time to use a platform.
Read the guide
WiseData Mail does this part for you
DNS assistant, automatic suppression and deliverability health panel on every plan.