Email Bounce Analysis: How to Diagnose and Fix Bounce Problems

What Bounce Analysis Tells You

Every bounce message contains diagnostic information. Most senders glance at the bounce count and move on, but the bounce details reveal exactly what went wrong and what to do about it.

A systematic approach to bounce analysis answers:

• Which addresses should be permanently removed?
• Which bounces are temporary and will resolve themselves?
• Is there a pattern pointing to an infrastructure or reputation problem?
• Are specific domains, segments or sources causing disproportionate bounces?

Bounce Categories

Hard bounces

Hard bounces are permanent delivery failures. The address will never accept your email.

Rule: Remove hard-bounced addresses after the first occurrence. Continuing to send to hard-bounced addresses damages your sender reputation.

Soft bounces

Soft bounces are temporary failures. The address exists but could not accept the message at that moment.

Rule: Retry soft bounces up to 3 times across separate sends. If the same address soft bounces 3 times in a row, treat it as a hard bounce and remove it.

Block bounces

Block bounces occur when the receiving server actively refuses your email, usually because of reputation or content issues.

Rule: Block bounces require you to fix the underlying problem (reputation, authentication, content) before retrying. Simply resending will make the problem worse.

Reading Bounce Messages

Anatomy of a bounce notification

A bounce notification (also called a non-delivery report or NDR) contains several useful fields:

From: Mail Delivery Subsystem <mailer-daemon@example.net>
To: sender@example.com
Subject: Delivery Status Notification (Failure)

The following message to <recipient@example.net> was
undeliverable.

Diagnostic-Code: smtp; 550 5.1.1 The email account that you
  tried to reach does not exist. Please try double-checking
  the recipient's email address for typos or unnecessary spaces.
  
Action: failed
Status: 5.1.1
Remote-MTA: dns; mx.example.net

SMTP status code structure

SMTP enhanced status codes follow the X.Y.Z format:

For example, 5.1.1 is a permanent (5) addressing (1) error: the mailbox does not exist.

Bounce Pattern Analysis

Looking at individual bounces is necessary but insufficient. Patterns across bounces reveal systemic issues.

By domain

By list source

By time

By bounce code

Building a Bounce Management Workflow

Step 1: Collect bounce data

Export bounce reports from your email sending platform. Most platforms provide bounce exports as CSV files containing:

• Bounced email address.
• Bounce code.
• Bounce message.
• Date and time.
• Campaign or send identifier.

Step 2: Categorise bounces

Sort each bounce into one of three categories:

def categorise_bounce(status_code):
    """Categorise a bounce by its status code."""
    first_digit = status_code[0]

    if first_digit == "5":
        # Permanent failure
        second_digit = status_code[2]
        if second_digit == "1":
            return "hard_bounce_address"
        elif second_digit == "7":
            return "block_bounce_policy"
        else:
            return "hard_bounce_other"
    elif first_digit == "4":
        return "soft_bounce"
    else:
        return "unknown"

Step 3: Apply rules

Step 4: Update your suppression list

Every address you remove due to bouncing should go onto a permanent suppression list. This prevents the address from being re-added if it appears in a future import:

def process_bounces(bounces, suppression_list, contact_list):
    """Process bounce records and update lists."""
    for bounce in bounces:
        category = categorise_bounce(bounce["status_code"])

        if category.startswith("hard_bounce"):
            suppression_list.add(bounce["email"])
            contact_list.remove(bounce["email"])
        elif category == "soft_bounce":
            contact_list.increment_soft_bounce(bounce["email"])
            if contact_list.soft_bounce_count(bounce["email"]) >= 3:
                suppression_list.add(bounce["email"])
                contact_list.remove(bounce["email"])
        elif category == "block_bounce_policy":
            contact_list.flag_for_review(bounce["email"])

Step 5: Analyse and report

After processing, generate a summary:

Preventing Bounces

Prevention is more effective than treatment:

Pre-send verification with Email Extractor

When building prospect lists from files and documents, extract addresses with Email Extractor first to deduplicate, then run the extracted list through a verification service before sending. Extraction and deduplication are a necessary first step but do not replace verification. An address can be correctly formatted, present in a legitimate document and still bounce because the mailbox no longer exists.

Acceptable Bounce Rates

If your bounce rate exceeds the action threshold, stop sending until you identify and fix the cause. Continuing to send into high bounce rates accelerates reputation damage.

Related Guides

• Understanding Email Bounce Codes
• Email Deliverability Troubleshooting
• How to Clean Your Email List
• Email List Sunset Policies
• Sender Reputation Explained