Bounce-Back Email: How to Read a Bounced Message and Its Error Code
You send an email and, a few seconds or a few hours later, a message lands in your inbox with a subject like "Undeliverable," "Delivery Status Notification (Failure)" or "Mail delivery failed." That's a bounce-back email. It looks technical, but it tells you exactly what went wrong, if you know where to look.
This guide shows you how to read one, what the most common error codes mean, and what to do about each.
What a bounce-back email is
When a mail server can't deliver your message, it sends a report back to you. Microsoft calls it a non-delivery report, or NDR, and notes it's "also known as a 'bounce message' or 'bounce-back message.'" Gmail labels it a Delivery Status Notification. Whatever the name, the report includes the address that failed, the server that refused it, and an error code explaining why.
One bounce-back on a single email you typed by hand is usually a typo. Lots of them after a campaign means your list needs cleaning.
How to read the error code
Look for a line with numbers like 550 5.1.1. The first number (550) is the server's basic reply. The second (5.1.1) is the "enhanced status code," defined in RFC 3463, and it's the more useful one. Read it in three parts:
- The first digit is the type of failure. A 4 means a temporary problem: RFC 3463 says "sending in the future may be successful." A 5 means a permanent failure that is "not likely to be resolved by resending the message in the current form." In everyday terms, 4 is a soft bounce and 5 is a hard bounce.
- The second digit is the area of the problem. 1 is the address, 2 is the mailbox, 4 is the network or routing, and 7 is security or policy.
- The third digit is the detail, such as "mailbox does not exist."
The bounce codes you'll see most
| Code | What it means | What to do |
|---|---|---|
| 5.1.1 | Bad mailbox address. RFC 3463: "The mailbox specified in the address does not exist." | Check for a typo. If it's right, the person has left: remove the address. |
| 5.1.10 | Microsoft's "recipient not found" for Outlook and Microsoft 365 addresses. | Same as 5.1.1: fix or remove. |
| 5.1.2 | Bad destination system: the domain "does not exist or is incapable of accepting mail." | Look for a misspelled domain (gmial.com). Otherwise remove it. |
| 5.2.1 | Mailbox disabled: it "exists, but is not accepting messages." | Usually an abandoned account. Remove it if it bounces again. |
| 4.2.2 | Mailbox full, a temporary failure. | Try again later. Remove it if it keeps bouncing for weeks. |
| 4.4.x / 4.7.x | Temporary network, routing or rate-limit problems. | Wait and resend. If it repeats, slow down your sending. |
| 5.7.1 | Delivery not authorized. RFC 3463: "The sender is not authorized to send to the destination." | Often a spam filter or a group that only accepts members. Check your SPF, DKIM and content, or contact the recipient another way. |
Microsoft's own list adds a warning: its servers also use 5.7.1 for other policy errors such as "Unable to relay," so read the words next to the code, not just the numbers.
Hard bounce or soft bounce: what to do next
Hard bounces (5.x.x) won't fix themselves. Remove the address, or correct it if you can see the typo. Mailchimp, for example, says it removes hard-bounced addresses from your audience straight away. Your email platform may do the same automatically.
Soft bounces (4.x.x) are often fine on the next try. Keep the address, but watch it: if the same address soft-bounces on campaign after campaign, treat it as dead.
For a deeper comparison, see hard bounce vs soft bounce, and for what a normal rate looks like, what is a good email bounce rate.
Check a list from $1.49
When you get lots of bounce-backs at once
A wave of bounce-backs after one campaign usually means one of three things:
- An old list. Addresses go stale as people change jobs and abandon inboxes. Mostly 5.1.1 codes.
- A list from somewhere else (an old CRM export, a purchased or scraped list). Expect many dead domains and fake addresses.
- A reputation or setup problem. If good addresses at one provider all bounce with 5.7.x codes, the problem is on your side, not theirs: check your SPF, DKIM and DMARC.
Google's sender guidelines tell senders to "automatically unsubscribe recipients who have multiple bounced messages," so ignoring bounce-backs can hurt your delivery to everyone else on the list.
How to stop bounce-backs before you send
The cheapest bounce is the one that never happens. Before a campaign, run the list through an email checker. It finds typos, dead domains, throwaway inboxes and mailboxes that no longer exist, so you can fix or remove them first. Read how to clean an email list for the full process.
Frequently asked questions
What is a bounce-back email?
It's an automatic message from a mail server saying your email couldn't be delivered. Microsoft calls it a non-delivery report (NDR). It includes an error code that explains why.
What does 550 5.1.1 mean?
The address doesn't exist. RFC 3463 defines 5.1.1 as a bad destination mailbox: the mailbox in the address does not exist. Check for a typo, then remove the address.
Should I resend after a bounce-back?
Only for temporary errors starting with 4, such as a full mailbox. Errors starting with 5 are permanent, so resending the same message won't work.
Why do I get bounce-backs from addresses that worked before?
People leave jobs and close accounts. An address that worked last year can be disabled today, which is why lists need checking before each big send.