# Hard bounce vs. soft bounce: what to check

> Read an email bounce reason and decide what to check before correcting an address or retrying.


**A hard bounce and a soft bounce are labels some email platforms use for messages that were not delivered: the first usually indicates a failure treated as permanent, while the second indicates a condition that may be temporary.** The label helps start the diagnosis, but the receiving server’s reason and your sending provider’s rules determine what to check.

In email, a bounce concerns delivery. In [GA4, bounce rate describes sessions that were not engaged sessions](/en/guides/ga4-bounce-rate/); for email, the notice means a receiving server rejected or could not deliver a message.

These labels belong to the provider. For example, [Mailchimp’s bounce documentation](https://mailchimp.com/help/soft-vs-hard-bounces/) describes how its own system classifies and handles hard and soft bounces; that policy does not define every platform’s behavior.

## What to check for a hard or soft bounce

Open the full error message and keep the status code, explanation, and receiving provider. Do not decide what to do from the category name alone.

- **Nonexistent address:** check whether the notice confirms that the mailbox does not exist and review how the address was collected. If the failure is permanent, correct the source or suppress that address under your platform’s rules; repeatedly resending will not fix invalid data.
- **Temporary condition:** a full mailbox or unavailable server may allow another attempt. Check how long and how often your provider retries; do not assume every platform uses the same policy.
- **Policy rejection:** this may involve the receiving server’s rules, sender reputation, or sender configuration. Read the full text before attributing a specific cause. A policy rejection does not prove the address is invalid.
- **Unknown reason:** keep the original response and check the provider’s report or support before classifying it yourself.

## Example: 8 bounces out of 200 attempts

**Fictional case.** After the provider’s retry period ends, a campaign report records 200 original messages sent to distinct recipients and 8 undelivered messages: **8 ÷ 200 × 100 = 4%**. The denominator counts each original message once; SMTP retries are not added as new sends. Reviewing the responses, you find three `5.1.1` codes for an invalid destination mailbox, two `4.2.2` codes for a full mailbox, two `5.7.1` policy rejections, and one notice the system does not classify.

The breakdown is: 3 out of 200 (1.5%) for invalid destination mailboxes; 2 out of 200 (1%) for full mailboxes; 2 out of 200 (1%) for policy rejections; and 1 out of 200 (0.5%) unclassified. Together, they make up all eight bounces, or 4%. The codes exist in the standard; their appearance and counts in this report are hypothetical.

The IETF’s `4.x.x` and `5.x.x` codes describe transient and permanent conditions in broad terms. For example, `4.2.2` means a full mailbox and `5.1.1` an invalid destination mailbox. The “hard” or “soft” label, however, depends on the system processing the notice. Do not map every class 4 to soft or every class 5 to hard without checking your provider’s rules. The [RFC 3463 standard](https://www.rfc-editor.org/rfc/rfc3463) also groups security and policy errors; `5.7.1` alone does not identify an invalid address or one specific cause.

## What to do with each group

In this case, verify the three addresses associated with `5.1.1` and suppress them if the server confirms they do not exist, following your email service provider’s (ESP’s) policy. For `4.2.2`, review the retry history and provider policy before deciding whether another send is appropriate. For the two `5.7.1` responses, read the full notice and check the receiving provider’s guidance. Gmail, for example, documents `5.7.1` rejections related to a suspended IP and recommends checking authentication and other sender requirements ([sender guidelines](https://support.google.com/mail/answer/81126?hl=en)). That example does not mean every `5.7.1` code has the same cause. Investigate the remaining notice before assigning it to hard or soft.

A report without a bounce also does not confirm that the message reached the primary inbox: the server may accept it and classify it as spam. If the issue repeats, compare codes, receiving domains, dates, and the full server response; the overall bounce rate does not explain the cause by itself.

The cover is an AI-generated illustration.

## Plan your next post in HeyMark.

Keep the idea, review the draft with your team, and see how it performed in the accounts you connected.

[Start free](https://app.heymark.ai) · [See how it works](https://heymark.ai/en/#product)

## Developer and agent resources

- [HeyMark MCP documentation](https://heymark.ai/en/mcp/)
- [llms.txt](https://heymark.ai/llms.txt)
- [Full site content for language models](https://heymark.ai/llms-full.txt)
- MCP protocol endpoint: `POST https://mcp.heymark.ai`
- OAuth protected-resource metadata: [/.well-known/oauth-protected-resource](https://mcp.heymark.ai/.well-known/oauth-protected-resource)
- MCP server card: [/server-card](https://mcp.heymark.ai/server-card)
