An email bounce means a receiving system did not accept or deliver a message as intended. The bounce message is not noise: it usually contains the reason and tells you whether the problem is permanent, temporary, sender-specific, or recipient-specific. The right response begins by saving the exact error text and identifying the stream that produced it.
Hard bounces versus soft bounces
A hard bounce is generally permanent. Common examples include a non-existent mailbox, invalid domain, or address that cannot receive mail. A soft bounce is usually temporary, such as a full mailbox, temporary receiving-server problem, rate limit, or transient policy issue. Providers use the terms differently, so rely on the actual error code and text rather than the label alone.
Read the bounce message
Preserve the complete delivery-status notification or sending-platform log. Look for the recipient address, receiving domain, SMTP status code, descriptive text, timestamp, and message ID. The code often starts with 4 for a temporary condition or 5 for a permanent condition, but context matters. Share this evidence with your provider if escalation is needed.
Check the recipient address and list source
For a hard bounce, confirm whether the address contains a typo, belongs to a former employee, or came from an old import. Suppress clearly invalid addresses promptly to protect list quality. Do not repeatedly retry a hard bounce or re-add it from an imported spreadsheet. Review the list-hygiene guide for a safe suppression process.
Check whether the problem affects one recipient or many
One failing mailbox may be a recipient issue. A pattern across a recipient domain can suggest a provider policy, DNS, reputation, or configuration issue. A pattern across all recipients may point to your sending platform, account status, authentication, or domain. Segment the evidence before making a broad change.
Review authentication for sender-related bounces
Some rejections occur because the sending domain is not authenticated or aligned as expected. Check a fresh message header from a successful test where possible, then review SPF, DKIM, and DMARC. Use the SPF check guide, the DKIM check guide, and the DMARC check guide before editing DNS.
Check reputation and sending behavior
High complaints, abrupt volume growth, invalid-address patterns, and a new sending identity can increase rejections or temporary deferrals. Reduce volume to a consent-based segment while you investigate. Authentication is important, but it does not make a purchased or stale list safe to mail.
Watch for temporary infrastructure issues
A soft bounce can result from a full recipient mailbox, temporary server outage, rate limit, or DNS problem. Retry only according to your platform’s normal policy. If the error points to your domain, compare recent changes to DNS, mail provider, certificate, and account status. Do not change unrelated records just because a recipient server had a temporary problem.
Use a controlled response
- Save the exact bounce evidence.
- Classify it as likely permanent, temporary, or sender-related.
- Suppress invalid addresses and investigate repeated patterns.
- Check authentication and account status when the sender is implicated.
- Test after one evidence-based correction.
Use the deliverability troubleshooting flowchart for the broader decision path. Run Beacon’s free domain check to review the public email-authentication foundation behind sender-related delivery failures.
Document recurring patterns
Track bounce categories by platform and recipient domain. A monthly pattern can reveal a stale integration, a broken form, or a list-acquisition problem before it becomes a larger reputation issue.