Email Bounce Back: What It Means and How to Fix It

An email bounce back is an automatic message telling you that your email was not delivered. The receiving mail server refused it, and the bounce message contains a code that says why. Most bounces come down to three causes: the address does not exist, the mailbox cannot accept mail right now, or the server rejected you as a sender.

This guide explains how to read the code inside a bounce, what to do for each common message, and how sales teams can stop bounces before they hurt their domain.

What does a bounce back email mean?

When you send an email, your mail server hands it to the recipient's mail server. That server can accept it, delay it, or refuse it. When it refuses, your own server sends you a report saying so. That report is the bounce back. Its technical name is a non-delivery report (NDR), and it usually arrives from an address like "Mail Delivery Subsystem", "MAILER-DAEMON" or "postmaster".

The part that matters is the error line. It normally looks like this:

550 5.1.1 The email account that you tried to reach does not exist.

There are two codes in that line:

• The three-digit reply code (550). Defined in RFC 5321, the standard that governs how email servers talk to each other. A code starting with 4 means a temporary failure. A code starting with 5 means a permanent failure. (RFC 5321)
• The enhanced status code (5.1.1). A more specific label that most large providers add. The first digit repeats the severity, and the rest narrows down the reason.

The text after the codes varies by provider, so read the codes first.

Hard bounce vs soft bounce

Every bounce falls into one of two groups.

Hard bounce: a permanent failure, usually a 5xx code. The address does not exist, the domain does not exist, or the server has decided it will not take your mail. Sending again will not help. Remove the address or fix the cause.

Soft bounce: a temporary failure, usually a 4xx code. The mailbox is full, the server is busy, or it is slowing you down. Your mail server will normally retry on its own for a while. If it keeps failing over several days, treat it like a hard bounce.

One wrinkle. Mailbox-full errors can arrive as either. Gmail, for example, uses 452 4.2.2 when an inbox is out of storage and 552 5.2.2 when the inbox is out of storage and inactive (Google Workspace Admin Help). The first is worth retrying. The second usually means nobody is reading that mailbox any more.

Common bounce messages and what they mean

Here are the bounce messages you are most likely to see, what each means in plain English, and what to do. The quoted wording comes from Google's own list of Gmail SMTP errors unless noted otherwise.

"Address not found" or 550 5.1.1

Gmail shows this as a big "Address not found" heading, with a line saying your message wasn't delivered because the address couldn't be found or is unable to receive mail. Underneath is the server response: "550 5.1.1 The email account that you tried to reach does not exist."

What it means: there is no mailbox at that address. It may be a typo, a guessed address, or someone who has left the company.

What to do: check the spelling first, especially the part after the @. If it is spelled correctly, the address is dead. Remove it from your list and find the person's current address. Do not keep sending to it.

550 5.2.1 "The email account that you tried to reach is inactive"

What it means: the account existed but has been disabled. At a company domain, this very often means the person left and IT switched the account off.

What to do: treat it as a hard bounce. Check whether the person has moved to a new company and look them up there.

550 5.4.1 "Recipient address rejected: Access denied" (Microsoft 365)

Microsoft says this error is generated because the recipient's email address is invalid. Exchange Online checks the address against the company's directory and rejects it at the edge if it is not recognised (Microsoft Support). Despite the "access denied" wording, this is usually not about you being blocked.

What to do: same as 5.1.1. Check spelling, then remove the address if it is correct.

552 5.2.2 or 452 4.2.2 "Mailbox full"

What it means: the recipient's inbox is out of storage. With the 4xx version, it is temporary. With Gmail's 552 5.2.2, the inbox is full and inactive.

What to do: for a 4xx, wait and let your server retry, or try again in a few days. For a full-and-inactive mailbox, stop sending. An inbox that has been full for long enough to be marked inactive is not being read.

554 or 550 5.7.x "Message rejected" or "blocked"

RFC 5321 describes 554 simply as "transaction failed", and 550 covers cases where the server refuses mail for policy reasons. The 5.7.x enhanced codes are the security and policy family. Two common Gmail versions:

• 550 5.7.1: "The user or domain that you are sending to (or from) has a policy that prohibits the email that you sent."
• 550 5.7.26: "Unauthenticated email from domain-name is not accepted due to domain's DMARC policy."

What it means: the problem is you, not the address. Your domain or IP may be on a blocklist, your authentication (SPF, DKIM, DMARC) may be broken, or the content tripped a filter.

What to do: check that SPF and DKIM pass for your sending domain and that you have a DMARC record. Check your domain and sending IP against public blocklists. If you are sending cold outreach, slow down and look at your list quality, because a block is often the end result of too many bounces and spam complaints. Our guide to cold email deliverability covers the setup in detail.

421 4.7.0 or 450 4.2.1 "Try again later"

Gmail uses 421 4.7.0 for messages like "Try again later, closing connection." and 450 4.2.1 for "The user you are trying to contact is receiving email too quickly."

What it means: a soft bounce. The server is not refusing the address, it is refusing the pace. This often happens when you send a lot of mail in a short burst from a new or low-reputation domain.

What to do: nothing immediately, your server will retry. If you see it often, slow down. Google's own guidance says that if messages start bouncing or being deferred, you should reduce volume until the error rate comes down (Gmail email sender guidelines).

Why is my email bouncing? A quick diagnosis

If you are asking "why is my email bouncing", start with how many emails are affected.

• One address bounces: the problem is that address. Look for 5.1.1, 5.2.1 or 5.4.1 and check for typos or a person who has left.
• Everything to one company bounces: that company's server is blocking you, or the domain has changed. Look for 5.7.x codes.
• Lots of different addresses bounce at once: your list is the problem, your domain is being blocked, or both. Check your authentication and your list source before you send another email.

How bounces hurt your sender reputation

Inbox providers watch what happens to your mail. A sender who keeps hitting addresses that do not exist looks like someone who bought or guessed a list. Over time that pattern drags down your domain's reputation, and once it drops, even your emails to valid addresses start going to spam.

Google's sender guidelines ask senders to remove recipients who have multiple bounced messages and to keep reported spam rates below 0.3% (Gmail email sender guidelines). Bounces and spam complaints usually travel together, since a list with many dead addresses tends to be a list of people who never expected to hear from you.

Bounces can also lead you into spam traps. A recycled spam trap is a closed mailbox that is later reactivated as a trap, often after senders ignored its hard bounces (Bird). Keep mailing a dead address long enough and you may end up mailing a trap.

What bounce rate is safe?

There is no single universal number, but email service providers publish the thresholds they enforce. Amazon SES recommends keeping your bounce rate below 5%. At 5% or higher it automatically places your account under review, and at 10% or higher it may pause your sending (Amazon SES documentation).

Treat 5% as the point where a provider is already worried, not as a target. For cold outreach from your own domain, the practical goal is to get as close to zero as you can, because you have no list-building history to protect you. If one campaign bounces more than a couple of percent, stop and clean the list before the next send.

How to prevent bounces in cold outreach

Most bounces in sales outreach are preventable. They come from the list, not from the email. And each one costs more than a lost message, as we show in the hidden cost of a wrong email address.

Verify every address before you send

Email verification checks with the receiving mail server whether a mailbox exists, without sending a message. Run it on every address before it goes into a sequence. Our post on what email verification actually tells you explains what the results mean and where they stop.

Re-verify old lists

A list that was clean six months ago is not clean today. People change jobs, companies change domains, and mailboxes get shut down. If a list has been sitting in your CRM or a spreadsheet for more than a few weeks, verify it again before using it. Here is why email lists decay faster than you think.

Do not guess addresses on catch-all domains

A catch-all domain accepts mail for any address, so a mail-server check will say "accepted" whether firstname@ exists or not. If you guess a pattern on a catch-all domain and send, you may find out it was wrong only when the bounce arrives later, or not at all. Only send to catch-all addresses that you have confirmed through a reliable source.

Remove hard bounces straight away

Set your sending tool to suppress any address that hard bounces. Never re-send to a 5.1.1 hoping it will work the second time.

Set up authentication and warm up new domains

SPF, DKIM and DMARC prevent the 5.7.x family of rejections. A new sending domain should start with low daily volume and build up gradually, which avoids the "try again later" deferrals.

Where prospiq fits

prospiq is built around this problem. You give it a person's name and company, and it returns their verified work email. Every email is checked with the mail server before you're charged. If a verified email still bounces, email support@prospiq.net with the bounced addresses within 30 days and the credits are put back in your account.

On catch-all domains, prospiq only returns an email that a data partner has confirmed for that person. Otherwise it returns nothing and charges nothing. And if you have an older list, saved emails are re-checked before being given out again if they were last verified more than 15 days ago.

If you want to test it on your own prospects, prospiq's Free plan gives you 20 credits, no card needed. For teams in India, paid plans start at Rs 2,399 a month plus GST. See pricing for details.

FAQ

What does a bounce back email mean?

It means your email was not delivered. The recipient's mail server refused it and your server sent you a report, called a non-delivery report, explaining why. The code in the report tells you whether the problem is the address, the mailbox, or your sending setup.

Why is my email bouncing back when the address is correct?

If the address is spelled correctly and still returns 5.1.1, 5.2.1 or 5.4.1, the mailbox no longer exists, usually because the person left the company. If you get a 5.7.x code, the address is fine but the server is rejecting you as a sender, often because of failed authentication or a blocklist.

Will a soft bounce eventually deliver?

Often, yes. Your mail server retries 4xx failures automatically, and many deliver within hours. If the same address keeps soft-bouncing over several days, stop sending to it and treat it like a hard bounce.

What is a good email bounce rate for cold email?

As close to zero as possible. Amazon SES puts accounts under review at 5% and may pause sending at 10%, so anything near those levels means your list has a serious problem. Verify every address before sending and re-verify anything older than a few weeks.

What should I do after a hard bounce?

Remove the address from every list and sequence right away. Then, if the person still matters to you, find their current work email and verify it before sending again.