barb, wire, fence, post, brown email
Photo by draconianimages on Pixabay

Deliverability

Part of Email deliverability, sender reputation and diagnosis

Investigating a sudden rise in bounced emails

Investigate a sudden bounce spike using SMTP replies, recipient groups, sending routes and a controlled follow-up.

This is an editorial pen name used by the publication, not a claim of an independently verified personal identity. Original editorial credit: Deliverability Desk.

When bounces rise suddenly, pause any planned repeat to the affected audience and inspect the receiver’s replies. Establish how many messages were attempted, which failed and whether failures cluster by recipient domain, error text or sending route. A headline rate or a platform’s “hard” and “soft” labels may conceal different causes.

Confirm what changed

Compare attempted-message and bounce counts with the same kind of send over recent weeks, using the same platform definitions, so the baseline is your own normal rate rather than a generic benchmark. Check whether the audience, list source or mix of recipient domains changed.

Note when failures began and whether they coincide with a new import, sending service or authentication change. A problem confined to one recipient domain should not be treated as list-wide without further evidence.

Key Bounce Metrics to Monitor

Attempted Messages
Compare current vs. recent weekly average
Hard Bounces
Identify if concentrated by domain or route
Soft Bounces
Check retry status and timing

Read the full reply code

An SMTP reply starting with 4 is a temporary negative response to a request; one starting with 5 is a permanent negative response to that request. A 4xx response may be retried and need not become a final bounce. The basic reply codes are defined in RFC 5321, and the enhanced status codes, with names such as bad destination mailbox address, in RFC 3463.

A 5xx response can still identify a correctable configuration fault. Enhanced codes and reply text add detail, while a platform’s bounce category may be approximate.

Reply patternExample codesFirst checkNext action
Address or mailbox does not exist550 with text such as "no such user"; enhanced status: bad destination mailbox addressSource and age of the addressSuppress addresses confirmed invalid and correct capture errors.
Temporary mailbox or server problem452, insufficient system storageExisting retry status and affected recipient domainsLet the sending service’s managed retry process run; avoid a duplicate campaign.
Authentication or policy rejectionEnhanced status: delivery not authorized, message refusedThe affected route’s From, SPF, DKIM and DMARC identitiesRepair the confirmed route or policy fault before retrying.
Rate limiting or unusual volume421, service not available, closing transmission channelTiming, volume and the receiver’s stated reasonFollow receiver guidance and the sender’s retry controls.

These are starting points, not universal meanings for every code. Read the accompanying text.

Find the common factor

Preserve the campaign report and exact diagnostic replies that the platform makes available. Record send time, campaign or automation, recipient domain, sending route, reply code and text, and final platform status. Sort the records by recipient domain and by reply code before changing the setup.

Mailchimp’s guidance says reading bounce headers (SMTP replies) can provide insight into why an address hard bounced. Check your platform’s available reports and capture the details you need while they are available.

Invalid-address replies concentrated after one upload suggest a source-data problem. Similar authentication rejections across campaigns using one service suggest a route problem.

When temporary failures concentrate at one receiver, investigate that receiver specifically and check the retry state. For Gmail, Google's sender guidelines say messages sent from IP addresses on a blocklist are more likely to be marked as spam, and point senders on a shared IP to Postmaster Tools to check that IP address's reputation.

Check that no retry or new campaign reintroduces unsubscribed or otherwise excluded contacts. Before sending again, check that you have the recipient’s permission and that the message is expected.

Correct and verify

Record the supported cause, correction and messages still pending. Suppress confirmed invalid addresses, repair configuration faults with the relevant provider, and avoid resending to people already reached.

After the change, inspect the next appropriate send by recipient domain and error type. Compare the underlying audience as well as its bounce rate; a smaller rate from a different population does not alone prove the fault was fixed.

More from Deliverability

Deliverability

What SPF, DKIM and DMARC each do

Learn what SPF, DKIM and DMARC check, how alignment works and why authentication does not guarantee inbox placement.