Why are my emails bouncing? A diagnostic walkthrough
· 6 min read · Email validation
Your emails are bouncing for one of five reasons: the mailbox doesn't exist, the domain doesn't exist or doesn't accept mail, the mailbox is full or disabled, the receiving server rejected you on policy (authentication, content, reputation), or it deferred you temporarily and eventually gave up. The bounce message tells you which. Read the three-digit SMTP code and the enhanced status code (like 5.1.1) in it, and you'll know whether to fix the address, fix your sending setup, or just wait.
First: is it one address, a few, or everything?
The pattern tells you where to look before you read a single bounce.
| Pattern | Most likely cause | Where to look |
|---|---|---|
| One recipient bounces | Typo, departed employee, dead mailbox | The address itself |
| A slice of a list bounces | Old or purchased list, bad import | List source and age |
| Everything to one provider bounces | You're blocked or failing their requirements | Authentication, reputation, that provider's postmaster docs |
| Everything to everyone bounces | Your domain, DNS or sending account is broken | Your own setup |
If everything broke on the same day, check your own side first. A lapsed domain registration, a DNS change that dropped your SPF or DKIM records, or a suspended account at your email service provider will bounce every message, and no amount of list cleaning fixes it.
How to read a bounce message
A bounce (formally a delivery status notification, defined in RFC 3464) is an email from a mail server, usually MAILER-DAEMON or postmaster, reporting that your message wasn't delivered. Ignore the friendly paragraph at the top and find the diagnostic lines:
Final-Recipient: rfc822; jane.doe@example.com
Action: failed
Status: 5.1.1
Diagnostic-Code: smtp; 550 5.1.1 <jane.doe@example.com>: Recipient address rejected: User unknown
Three parts matter:
- The basic reply code (
550). The first digit is what counts:5is a permanent failure (hard bounce),4is temporary (soft bounce). RFC 5321 defines these. - The enhanced status code (
5.1.1). Defined in RFC 3463, the middle digit names the subject:1is addressing,2is the mailbox,4is network and routing,7is security and policy. - The human text ("User unknown"). Servers word this differently, but it often contains the most specific hint, including links to the provider's help pages.
If you use an email service provider, its dashboard usually shows the same diagnostic per bounce. Look for the raw code, not just the provider's "hard" or "soft" label. Our SMTP bounce codes reference lists the common ones.
Cause 1: the mailbox doesn't exist
The most common hard bounce. Codes: 550 5.1.1, sometimes 550 5.1.0 or a bare 550 with "user unknown", "no such user" or "recipient not found".
Why it happens:
- Typos at capture.
jane@gmial.comorjane.doe@acme.coinstead of.com. Form typos never fix themselves. - People leave jobs. Work addresses die when someone changes employer. B2B list decay covers how fast this adds up.
- Guessed or scraped addresses.
firstname.lastname@patterns that were never real. - Fake signups. Someone typed
asdf@asdf.comto get past your form.
Fix: suppress the address permanently. Never retry a 5.1.1. Then fix the source: verify at capture, and verify lists before you send to them.
Cause 2: the domain doesn't exist or doesn't take mail
Codes: 5.1.2 ("bad destination system address"), 5.4.4 ("unable to route"), 5.1.10 (null MX, from RFC 7505), or bounces from your own server saying it couldn't resolve the domain.
Companies get acquired and retire their domain. Startups shut down and let it lapse. Some domains are registered but never set up for mail, or publish a null MX to say so explicitly. All addresses at these domains are dead. Suppress them, and if you see many, consider removing the whole domain from your list. Checking MX records shows how to test for this in advance.
Cause 3: the mailbox is full or disabled
Codes: 552 or 5.2.2 (over quota), 4.2.2 (temporary version), 5.2.1 (mailbox disabled).
A full mailbox is often a sign of an abandoned account: nobody is reading it and nobody is clearing it. Providers treat over-quota differently; some send it as a soft bounce and keep retrying, some as a hard one. A disabled mailbox usually means the provider or company closed the account.
Fix: a single full-mailbox bounce is worth one retry on your next send. Repeated ones mean the address is abandoned, so suppress it. Suppress disabled mailboxes immediately.
Cause 4: the receiver rejected you on policy
This is the category where the address is fine and the problem is you. Codes start with 5.7 (or 4.7 when temporary):
- Authentication failures. Gmail, for example, documents rejecting unauthenticated mail with a
5.7.26error in its email sender guidelines. Check that SPF, DKIM and (for bulk senders) DMARC are set up and aligned for your From domain. - Reputation and blocklists. The text often names the blocklist (Spamhaus and others) or says "poor reputation". Check the listing and follow the delisting process. Then fix what caused it, which is often a bad list.
- Content filters. The receiver's filter rejected the message itself: a link to a flagged domain, a suspicious attachment.
- Recipient-side rules. A company that only accepts mail from known senders, or a user who blocked you.
Policy bounces aren't evidence that the address is bad, so don't suppress based on them alone. Fix the cause and resend later. Our article on Gmail and Yahoo bulk sender requirements covers what those two providers expect.
Cause 5: temporary failures that ran out of time
Codes: 421, 450, 451, 452 and the 4.x.x enhanced codes. Greylisting, rate limiting, a server that's briefly down.
Your sending server retries these automatically, typically for days. If it never succeeds, you get a final bounce, often with 4.4.7 ("delivery time expired") or a message saying it gave up. One timed-out soft bounce isn't proof the address is dead. Several in a row for the same address usually are. Hard bounce vs soft bounce has a suppression rule of thumb.
If you get many 421 or 4.7.x deferrals from one provider, you're sending too fast for your reputation there. Slow down. Gmail's guidelines say that if messages start bouncing or being deferred, reduce the sending volume until the error rate decreases.
How to fix the list once you know the cause
When bounces are clustered in addresses (causes 1 to 3), the list is the problem. In order:
- Suppress every hard bounce now. Export them from your sender and add them to a permanent suppression list, not just an "unsubscribed" tag that someone can undo.
- Find where the bad addresses came from. Sort bounces by source: signup form, an import, a CSV from an event, a purchased list. One source usually accounts for most of them.
- Verify the rest of that source before the next send. A verifier checks the domain, MX records and the mailbox (without sending) and returns a status per address.
- Decide what to do with uncertain addresses. Catch-all and unknown results aren't bad, but they aren't confirmed either. Send to them in a smaller separate batch.
- Fix capture. Add verification and a typo suggestion to the form that produced the bad data.
Here is step 3 with pingutil's batch endpoint, which takes up to 50 addresses per call:
curl -s https://pingutil.com/v1/verify/batch \
-H "Authorization: Bearer $PINGUTIL_KEY" \
-H "Content-Type: application/json" \
-d '{"emails": ["jane.doe@example.com", "sam@gmial.com", "info@acme.io"]}' \
| jq -r '.results[] | [.input, .status, .reason, (.did_you_mean // "")] | @tsv'
Suppress invalid (reasons like mailbox_not_found, no_domain, null_mx, mailbox_disabled). Keep valid. Segment risky (accept_all, role_based, mailbox_full) and unknown into a cautious batch. If you'd rather not write code, the dashboard accepts a CSV upload, and the live verification demo shows what a single result looks like. Email verification statuses explained covers every reason code.
A quick triage checklist
- All mail bouncing? Check domain registration, DNS, SPF/DKIM and your ESP account status.
- One provider bouncing? Read their sender docs and look for
5.7.xcodes. - A segment bouncing? Find its source, suppress hard bounces, verify the rest.
- Only soft bounces? Slow down and let retries work. Suppress addresses that soft-bounce repeatedly.
- Bounces keep coming back from new signups? Verify at the form, not after the fact.
Questions people ask
- Why are my emails bouncing back when the address is correct?
- If the address is right, the bounce is usually about you rather than the recipient: missing SPF or DKIM, a sending IP or domain on a blocklist, a message the receiver's filter rejected, or a temporary rate limit. Read the enhanced status code in the bounce. A 5.7.x code points to policy or authentication, not the mailbox.
- Why are all my emails suddenly bouncing?
- When every message bounces at once, look at your own setup first: an expired domain, a broken DNS change that removed SPF or DKIM records, an account suspended by your email provider, or your sending IP being listed. A sudden change across all recipients is almost never a list problem.
- Do bounced emails hurt my sender reputation?
- Hard bounces to addresses that don't exist do, because mailbox providers read a high rate of them as a sign of a poorly kept list. A few bounces are normal. Suppress every hard-bounced address so you never send to it twice.