A bounced email can look like a simple yes-or-no verdict: delivered or not. In practice, a bounce is a clue about what happened at a particular point in the delivery process. A temporary problem, such as a recipient mailbox being full, may clear and allow another attempt. A permanent problem, such as an address that does not exist, usually needs a correction first. The labels are useful, but not conclusive on their own. Read the full bounce notice, identify the affected address and reason, then choose a response that fits the evidence.
The useful bits
- A soft bounce usually points to a potentially temporary delivery problem.
- A hard bounce often means the address or destination needs correction.
- Use the detailed bounce message, not just its label, to decide what to do.
The short version: temporary versus persistent
A soft bounce generally describes a message that could not be delivered for a reason that may be temporary. The receiving system might be unable to accept mail right now, or the recipient’s mailbox might be full. Depending on the sender’s mail service, it may retry delivery for a period of time. A soft bounce is not a promise that a later attempt will succeed.
A hard bounce generally signals a problem that is unlikely to resolve without a change. An invalid or misspelled address is a common example: retrying the same message to the same address does not fix the spelling. A hard bounce may also reflect a destination or policy issue, so check the details before deciding what needs to change.
Read the explanation, not only the label
Bounce terminology and status codes can differ between mail systems. One system’s label may not tell the whole story, and a brief notice may leave out useful context. Look for the recipient address, the reason text, any status or error code, and whether the notice says the failure is temporary or permanent. If the message includes a suggested action, consider it alongside the rest of the explanation.
Treat the notice as evidence about that delivery attempt, not as a universal statement about the address. A full mailbox can become available later; an address that appears invalid could have been mistyped. Conversely, a temporary label does not mean the message will eventually arrive. If the notice is unclear, avoid guessing from the label alone.
What to do when a failure may be temporary
For a plausible temporary issue, first check whether the sender’s mail service is already retrying. Sending the same message repeatedly can create duplicates if an earlier attempt is still in progress. If the bounce says the mailbox is full, you can wait and try again later, or ask the recipient through another appropriate channel whether they can receive mail. If the notice points to a temporary receiving-system problem, waiting may be more useful than changing the address.
When you do retry, use the same verified recipient address and a single, clear message. If a later attempt also fails, compare its details with the first notice. A changed error can indicate the delivery problem has changed; the original soft-bounce label by itself cannot establish that.
What to do when the address may be wrong
For a likely hard bounce, check the address against a reliable record or ask the intended recipient to confirm it. Look closely for a missing character, an extra space, or a wrong domain. Do not assume that a plausible-looking address belongs to the person you intend to reach. Correct the address only when you have a trustworthy basis for doing so, then send the message to the corrected destination.
If the address is confirmed but the bounce still indicates a permanent failure, keep the full notice and ask the recipient or their mail administrator to investigate the destination-side problem. Repeatedly resending unchanged mail is unlikely to help when the underlying reason remains unresolved.
A practical decision check
Before taking action, work through this short checklist. It helps separate a temporary interruption from a problem that needs correction without treating either label as definitive.
- Match the bounce to the exact recipient; a message sent to several people may fail for only one address.
- Read the reason and any code in the full notice, not just the subject line or soft/hard label.
- For a likely temporary cause, check whether a retry is pending and avoid repeated manual sends.
- For a likely permanent cause, verify and correct the address or ask the receiving side about the stated problem.
- After a change or later retry, check the new delivery status and confirm with the recipient when appropriate.
You send a message to [name]@example.com and receive a notice saying the mailbox is full. That points to a potentially temporary issue: check whether another attempt is pending, then wait or contact the recipient another way. If the notice instead says the address cannot be found, verify the spelling with a reliable source before sending again. After retrying to a confirmed address, review the new status; do not infer success merely because the earlier bounce disappeared.
How to tell whether your next step helped
After waiting, correcting an address, or contacting the recipient, look for the status of the new attempt or any later bounce notice. A notice that reports another failure means delivery has not been confirmed by that notice. If the sender’s system reports delivery, that still does not establish that the person has read the message or that it reached the inbox they check. For an important message, ask the recipient to confirm receipt through an appropriate channel.
Keep the original and any later bounce details together if you need help diagnosing the issue. The useful comparison is the stated reason and recipient for each attempt, along with what changed between them. That gives you a clearer next step than repeatedly sending the same message based only on a soft- or hard-bounce label.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction