Why are my emails bouncing?
Emails bounce for two broad reasons: the address can't receive mail (it doesn't exist, the domain is gone, the mailbox is full), or the receiving server refused your message (failed authentication, a blocklisted IP, content or volume). The code in the bounce message tells you which, and each needs a different fix.
By MailVet team
Start with the bounce code
Every bounce comes with a reason, usually an SMTP reply code followed by an enhanced status code, like 550 5.1.1. You'll find it in the bounce message (also called a non-delivery report) that lands in your inbox, or in the bounce report of your email platform or sequencer.
Read the enhanced code from left to right. The first digit is the class: 5 is a permanent failure (a hard bounce) and 4 a temporary one (a soft bounce) that the sending server will retry. The middle number is the area: 1 the address, 2 the mailbox, 3 the mail system, 4 network and routing, 5 the SMTP protocol, 6 the message content and 7 security or policy. The last number narrows it down.
That middle number answers the most useful question: is the problem the address, or is it you? Codes in the x.1 and x.2 families are about the recipient. Codes in x.7 are about the sender: your authentication, your IP or your content.
The common causes
The mailbox doesn't exist
A typo, someone who left the company, or an address made up at signup. The most common hard bounce. Remove it; it won't start working.
The domain doesn't exist or takes no mail
An expired domain, a misspelled one like gmial.com, or a domain with no mail servers. Fix the typo if the intent is obvious, otherwise remove it.
Full or disabled mailbox
Over quota, or switched off by the provider. Full mailboxes are often abandoned ones. Retry later, and suppress the address if it keeps happening.
Failed SPF, DKIM or DMARC
Your message couldn't be authenticated as coming from your domain. Gmail and Yahoo have required authentication since 2024, with stricter rules for bulk senders, and unauthenticated mail can be refused outright.
A blocklisted IP or domain
The receiving server refused you because of your sending reputation, often with text naming the blocklist. The address may be perfectly valid; the problem is on your side.
Volume, rate or content
Sending too much too fast earns temporary 4.7.x deferrals, oversized messages get 5.3.4, and spam-like content can be refused with 5.7.1. Slow down, warm up new domains, and trim attachments and link-heavy templates.
Bounce codes and what they mean
| Code | Meaning | Usual cause | What to do |
|---|---|---|---|
| 5.1.1 | Bad destination mailbox | The address doesn't exist | Remove it; don't retry |
| 5.1.2 | Bad destination system | The domain doesn't exist or can't receive mail | Fix the typo or remove it |
| 5.1.3 | Bad destination address syntax | A malformed address in your list | Fix or remove it |
| 5.2.1 | Mailbox disabled | Account closed or suspended | Remove it |
| 4.2.2 | Mailbox full (temporary) | Over quota | Let it retry; suppress if it repeats |
| 5.2.2 | Mailbox full (permanent) | Over quota and the server won't wait; often abandoned | Suppress; re-verify before the next send |
| 5.4.1 (Microsoft 365) | "Recipient address rejected: Access denied" | Usually the recipient doesn't exist in that organisation | Treat it like 5.1.1 |
| 4.4.7 / 5.4.7 | Delivery time expired | The sending server retried until it gave up | Check the domain still receives mail; verify the address |
| 4.7.x | Temporary policy deferral | Greylisting, rate limiting or reputation checks | Slow down; retries usually get through |
| 5.7.1 | Delivery not authorized | Blocklisted IP, recipient policy, or content judged as spam | Read the text: fix reputation or content |
| 5.7.23 | SPF validation failed | The sending server isn't in your SPF record | Add your sending service to SPF |
| 5.7.26 | Multiple authentication checks failed | The message failed DMARC: no aligned SPF or DKIM pass | Turn on DKIM signing and align your domains |
Enhanced status codes are defined in RFC 3463 and later RFCs. Providers don't always use them consistently, so read the text after the code as well; it usually names the actual problem.
How to fix a bounce problem
- 01
Pause the affected sends
If bounces jumped suddenly, stop sending from that domain or inbox first. Pushing through a bad list multiplies the damage.
- 02
Group bounces by code
Separate address problems (5.1.x, 5.2.1) from sender problems (5.7.x) and temporary ones (4.x.x). Each group has a different fix.
- 03
Suppress the dead addresses
Add every hard-bounced address to your sending tool's suppression list and mark it bounced in your CRM, so the next import doesn't bring it back.
- 04
Verify the rest of the list
The addresses that haven't bounced yet came from the same source. Verify them before the next send; /email-list-cleaning explains how.
- 05
Fix authentication
Make sure SPF includes every service that sends for you, DKIM signing is on, and a DMARC record is published. The 5.7.2x codes point here.
- 06
Check reputation, then ramp back up
For 5.7.1 blocks, look up your IP and domain on the blocklist the bounce names, and check Google Postmaster Tools for Gmail. Resume at a lower volume once the cause is fixed.
Why a verified list can still bounce
Verification removes the bounces caused by bad addresses, which are the ones you can prevent. It can't stop all of them:
- Addresses decay. A list verified three months ago has had three months of job changes since. Verify right before you send.
- Some servers accept first and bounce later. That's typical of catch-all domains, which is why MailVet checks the mailbox behind them instead of reporting accept-all. See /catch-all-email-verification.
- Policy bounces aren't about the address. A 5.7.x refusal means the receiving server rejected you. Verification can't fix authentication or reputation.
- Full mailboxes come and go. A mailbox over quota today may accept mail next week, or never again.
How many bounces is too many?
There's no single official threshold. Gmail and Outlook don't publish a bounce rate they act on, and every email platform sets its own limits. Amazon SES, for example, places an account under review once its bounce rate reaches 5%.
A widely used rule of thumb for marketing and cold email is to keep bounces under 2%, and to treat any sudden jump as a reason to stop and investigate, whatever the absolute number. Hard bounces are the part of that number list verification controls; how they differ from soft bounces, and how platforms treat each, is covered in /guides/hard-bounce-vs-soft-bounce.
Email bounce questions
What does 550 5.1.1 mean?
The receiving server says the mailbox doesn't exist. It's a hard bounce: the address is misspelled, was deleted, or never existed. Remove it from your list; retrying won't help.
Why are my emails bouncing back from Gmail?
The most common reasons are an address that doesn't exist (5.1.1), mail that failed authentication (5.7.26 or similar), and rate or reputation limits (temporary 4.7.x errors or 5.7.1 refusals). Gmail's bounce text includes a short explanation, so read past the code.
Can bounced emails hurt my sender reputation?
Yes. Mailbox providers notice when your messages go to addresses that don't exist, because a high rate suggests an old or bought list. Repeated hard bounces make it more likely that your next messages are filtered to spam or refused.
Will verifying my list stop all bounces?
It stops the ones caused by bad addresses: mailboxes and domains that don't exist, and dead addresses on catch-all domains. It can't prevent bounces caused by authentication, blocklists or content, and addresses can go bad after they're verified.
What's the difference between a hard and a soft bounce?
A hard bounce is permanent (5.x.x codes), so remove the address. A soft bounce is temporary (4.x.x codes), such as a full mailbox or a busy server, and is retried automatically. Our hard bounce vs soft bounce guide covers the details.
Stop the bounces you can prevent
Verify your list before the next send, catch-all addresses included. Your first 100 checks are free.
Related
- Hard vs soft bounces
- Email list cleaning
- Bulk email verifier
- Catch-all verification
- How to verify an email
Last updated November 13, 2026