
A hard bounce vs soft bounce comes down to whether an email delivery failure is likely permanent or temporary. A hard bounce usually means the address cannot receive mail, so remove it from future campaigns; a soft bounce may resolve on its own, so check the reason and retry according to your email platform’s rules.
Hard bounce vs soft bounce: the practical difference
An email service provider (ESP) classifies a bounce using the receiving mail server’s response. A hard bounce is generally a permanent failure. A soft bounce is generally temporary, but repeated soft bounces can be a sign that an address is no longer usable or that your sending is being refused.
| Type | What it usually means | What to do |
|---|---|---|
| Hard bounce | The address is invalid, the domain does not exist, or the server permanently refuses delivery. | Suppress the address from marketing sends and investigate how it entered your list. |
| Soft bounce | The mailbox is full, the receiving server is temporarily unavailable, or the message is deferred or temporarily refused. | Let your ESP handle reasonable retries, then review repeated failures before sending again. |
These labels are useful, but they are not a diagnosis by themselves. The same broad category can cover different server responses, and ESPs may apply different retry and suppression rules. Check the bounce reason or SMTP response in your campaign report when it is available.
Common causes and what bounce messages tell you
Why hard bounces happen
A mistyped address is a common cause: for example, a customer enters [email protected] instead of [email protected]. Hard bounces can also happen when an employee leaves and their work address is closed, a domain expires, or a recipient server rejects mail for a permanent policy reason.
Look for responses in the 5xx family, such as a 550 response, but don’t assume every 5xx message has the same meaning. The accompanying text matters. A response may indicate an unknown recipient, a blocked sender, or another issue that needs a different fix.
Why soft bounces happen
A full mailbox, temporary server outage, message-size limit, or short-lived receiving-server restriction can cause a soft bounce. A server may also defer mail when it is busy or does not trust the sending domain yet. Responses in the 4xx family commonly indicate a temporary problem, but read the full response and your ESP’s explanation.
One soft bounce does not necessarily mean a subscriber is lost. Several soft bounces over multiple campaigns deserve attention: the mailbox could be abandoned, or your domain’s authentication, sending pattern, or message content may need review. Don’t keep retrying manually without understanding your platform’s suppression policy.
What to do after a hard bounce
- Suppress the address promptly. Most ESPs automatically stop sending to addresses they classify as hard bounces. Confirm that this address is on your suppression list before the next campaign. Never delete the evidence and re-import the same address without a valid correction.
- Read the reason. Check whether the response says the recipient does not exist, the domain is invalid, or your message was refused for a policy or reputation reason. If multiple valid addresses at one business domain bounce, investigate the domain or sending issue instead of treating every failure as a typo.
- Trace the source. Review the signup form, checkout, spreadsheet, or point-of-sale import that added the address. For a retail store, check whether staff mistyped an email during a purchase. For a service business, review whether an appointment form accepts obvious spelling errors.
- Correct only with reliable information. If the customer has provided a new address through a trusted channel, update the record and retain the appropriate consent history. Don’t guess the correct spelling or try small variations of an address.
- Fix a pattern, not just a record. If hard bounces arrive in a cluster after importing a list, stop the next bulk send. Check the list’s origin and permission, remove invalid records, and review your domain setup and recent sending activity.
For a local bakery, a bounced order update is not a reason to keep emailing a bad address. Contact the customer through the phone number they supplied or another appropriate channel, ask them to confirm the correct email, and update it only after verification.
What to do after a soft bounce
Start by checking whether your ESP will retry delivery automatically. Many platforms make a limited number of attempts and then suppress or temporarily pause an address. Avoid repeatedly uploading the same soft-bounced contacts to bypass that behavior; it can add pressure without solving the underlying problem.
- Check whether the failure is isolated to one recipient or affects many addresses at the same provider or domain.
- Review the response text for clues such as mailbox full, server unavailable, message too large, or temporary policy rejection.
- If one person’s address fails once, let the normal retry process run and monitor the next report.
- If the same address soft-bounces repeatedly, pause marketing sends to it and use a permitted alternate channel to request an update.
- If many subscribers soft-bounce together, investigate your sending domain, authentication records, message size, and recent changes before resuming.
Suppose a landscaping company sends a seasonal service reminder and several customers at the same property-management firm bounce. That pattern may point to a company mail server issue rather than several unrelated bad addresses. Check the response details and contact the firm through its established business channel before changing records or sending again.
Use a simple bounce-response routine
A consistent process makes bounce handling easier for a small team and prevents a rushed campaign from turning into repeated delivery attempts.
| When | Check | Decision |
|---|---|---|
| After every campaign | Hard and soft bounce counts, reasons, and affected domains | Suppress hard bounces; identify any unusual cluster. |
| Before the next send | Suppression list, recent imports, and unresolved server errors | Do not re-add suppressed addresses or send into a known issue. |
| When a pattern appears | Signup source, permission, domain authentication, and message changes | Pause, correct the likely cause, and monitor the next send. |
Keep a brief internal record of what happened and what changed. It can be as simple as “checkout import had a typo-heavy batch; corrected form validation; hard bounces suppressed.” This helps the next person distinguish a one-off recipient problem from a recurring list or configuration issue.
Prevent avoidable bounces without overreacting
Collect addresses carefully at the point of signup. Show the address back to the customer on checkout or appointment forms, and make corrections easy. For higher-risk signups, use a confirmation step before adding the address to regular marketing campaigns. Never buy or scrape lists: even if some addresses accept mail, you may lack permission and attract complaints or invalid contacts. Review your email permission and anti-spam practices as part of list hygiene.
Keep your sending domain’s authentication configured and make sure your ESP uses it as intended. Send to people who expect your messages, maintain a steady cadence, and remove addresses that repeatedly fail. If you have a seasonal business, such as a tax preparer or holiday gift shop, don’t wait until the busiest period to import an old list and send to everyone at once.
Your ESP’s campaign report and suppression tools are often enough to handle routine bounces. Native mailbox tools can help you verify DNS records and investigate server responses, but they do not replace permission checks or your ESP’s delivery logs. Use the receiving server’s response, the pattern across recipients, and your platform’s policy together; no single bounce label tells the whole story.
A practical email platform option
If you want bounce prevention to sit alongside campaign work, MailFlow offers automatic warm-up, a brand domain on every email, and a spam check before sending. These tools can support a more deliberate sending process, but they do not make an invalid address valid or remove the need for permission and list maintenance. See the MailFlow help center for product guidance.
Conclusion: act on the reason, not just the label
For a hard bounce, suppress the address and investigate its source. For a soft bounce, allow normal retries, review the server response, and respond if the problem repeats or affects a group. Start with your latest campaign report: check the bounce reasons, confirm the suppression list, and fix any repeated source or sending issue before your next send.
Frequently asked questions
Should I remove a hard-bounced email address?
Yes. A hard bounce usually means the address cannot receive mail, so suppress it from future marketing sends. Check the bounce reason first, especially if many addresses at the same domain fail, because a broader server or sender-policy issue may be involved. Only update the record if the person confirms a valid replacement address through a trusted channel.
How many soft bounces are too many?
There is no universal number because email platforms use different retry and suppression rules, and server responses vary. Let your ESP’s normal retry process run, then look for repeated failures at the same address or a cluster affecting many recipients. Repeated soft bounces should prompt you to pause sends to those addresses and investigate the stated reason.
Can a soft bounce become a hard bounce?
Yes. A temporary delivery problem may later be treated as permanent, or repeated soft bounces may lead an email platform to suppress the address. The classification can depend on the server’s response and the ESP’s rules. Check campaign reports over time rather than assuming one soft bounce will always remain temporary.
Do bounces hurt email deliverability?
A high or repeated rate of failed delivery can be a warning that your list, sending practices, or domain setup needs attention. It does not mean every isolated bounce causes a deliverability problem. Suppress hard bounces, avoid repeatedly mailing unresolved soft bounces, and investigate sudden increases or failures concentrated at particular domains.
Should I email someone to ask them to fix a bounced address?
Don’t send another email to an address that has failed. If you have a permitted phone number, customer account, or other established contact method, you can ask the person to confirm or update their email there. Use the corrected address only after the person provides it, and keep the appropriate consent and record history.

Author
Founder of MailFlow, software engineer working across the full stack and every major programming language, specialising in AI automation, email deliverability and SEO.
Related articles
Email List Cleaning: How to Verify Addresses and Handle BouncesA practical guide to cleaning an email list: spot invalid addresses, manage bounces, reduce spam-trap risk, and keep your subscriber records useful.
Email Verification: Why You Should Check Addresses Before SendingLearn what email verification checks, why it matters for deliverability, and how to clean a list without treating verification as permission to send.
Fake Email Opens: Understand Bots, Apple MPP, and ClicksApple Mail Privacy Protection and security scanners can make open rates misleading. Learn how to spot artificial activity and measure real engagement.
Email Scanner Clicks: How Security Tools Distort Your StatsEmail security tools can visit links before subscribers do, making click reports misleading. Learn how to spot scanner activity and measure genuine engagement.