What Is a Bounce Back Email and How to Fix It

You hit send on an important email and minutes later you get a confusing reply from "Mail Delivery Subsystem" or "MAILER-DAEMON" telling you the message was not delivered. That is a bounce back, and it is one of the most frustrating things about email.

The good news: bounce messages tell you exactly what went wrong, if you know how to read them. This guide explains what bounces are, why they happen, and how to fix the most common causes.

What Is a Bounce Back Email?

A bounce back (also called a Non-Delivery Report, NDR, or Delivery Status Notification, DSN) is an automated reply from a mail server telling you that your email could not be delivered. The reply comes from the receiving server or your own sending server, depending on where the problem occurred.

Think of it like a letter being returned by the post office with a note explaining why it could not be delivered: wrong address, mailbox full, or access denied.

Hard Bounces vs. Soft Bounces

Not all bounces are the same. The distinction between hard and soft bounces matters because they require different responses.

Hard Bounces (Permanent Failures)

A hard bounce means the email cannot and will not be delivered, no matter how many times you retry. Common causes include:

• The email address does not exist. The mailbox was never created, or it was deleted. This is the most common hard bounce.
• The domain does not exist. The part after the @ sign is not a real domain, or its DNS records are missing.
• The server permanently refuses delivery. The recipient's server has a policy that blocks your message (e.g., your domain is blacklisted).

Hard bounces produce SMTP status codes starting with 5xx (500-series), indicating a permanent error.

Soft Bounces (Temporary Failures)

A soft bounce means the email could not be delivered right now, but the problem might resolve itself. Common causes include:

• Mailbox is full. The recipient has exceeded their storage quota.
• Server is temporarily down. The receiving mail server is offline or overloaded.
• Message is too large. The email (including attachments) exceeds the recipient's server limit.
• Greylisting. The server intentionally rejects the first delivery attempt to filter out spam, expecting legitimate servers to retry.
• Rate limiting. You have sent too many emails to that server in a short time.

Soft bounces produce SMTP status codes starting with 4xx (400-series), indicating a temporary error.

How to Read a Bounce Message

Bounce messages look intimidating, but the useful information is usually in one or two lines. Here is what to look for:

The Status Code

The most important piece of information is the three-digit SMTP status code. Here are the ones you will encounter most often:

• 550 — "Requested action not taken: mailbox unavailable." Usually means the address does not exist.
• 551 — "User not local." The server does not handle mail for that address.
• 552 — "Requested mail action aborted: exceeded storage allocation." The mailbox is full.
• 553 — "Requested action not taken: mailbox name not allowed." The email address format is invalid.
• 554 — "Transaction failed." A general rejection, often due to content filtering or blacklisting.
• 421 — "Service not available, closing transmission channel." The server is temporarily offline.
• 450 — "Requested mail action not taken: mailbox busy." Temporary issue, try again later.
• 451 — "Requested action aborted: local error in processing." A temporary server error, often greylisting.
• 452 — "Requested action not taken: insufficient system storage." The server is running out of disk space.

Enhanced Status Codes

Many servers also include enhanced status codes in the format X.Y.Z (like 5.1.1 or 4.7.1). These provide more detail:

• 5.1.1 — Bad destination mailbox address (the address does not exist).
• 5.1.2 — Bad destination system address (the domain does not exist).
• 5.2.2 — Mailbox full.
• 5.7.1 — Delivery not authorized, message refused (policy rejection or blacklist).
• 4.7.1 — Delivery not authorized, message refused temporarily (greylisting or rate limiting).

The Human-Readable Part

Most bounce messages also include a plain-English explanation after the code. Something like: "The email account that you tried to reach does not exist" or "Message rejected due to SPF failure." Read this line first — it often tells you everything you need to know.

Common Reasons Emails Bounce and How to Fix Them

1. Typo in the Email Address

This is the most common cause of bounces, and the easiest to fix. Double-check the address character by character. Common mistakes include swapping letters (gmial.com instead of gmail.com), missing a letter, or using the wrong domain extension (.com vs .org).

Fix: Correct the address and resend.

2. The Mailbox Does Not Exist

The address was valid at some point but the account has been deleted. This is common with work email addresses after someone leaves a company.

Fix: Try to find an alternative address for the person. If it is a business contact, try their company's general contact address.

3. Recipient Mailbox Is Full

The recipient has used up their storage quota. This is a soft bounce, meaning the email may be delivered later if the recipient frees up space.

Fix: Wait a day and try again. If it still bounces, contact the person through another channel and let them know their mailbox is full.

4. Your IP or Domain Is Blacklisted

If your sending IP address or domain appears on a blacklist (also called a blocklist), receiving servers may reject your email outright. This can happen if your account was compromised and used to send spam, or if your email provider's shared IP was abused by another user.

Fix: Check blacklist databases like MXToolbox, Spamhaus, or Barracuda. If you are listed, follow the delisting process (each blacklist has its own procedure). Ensure your account has not been compromised, and that your domain has proper SPF, DKIM, and DMARC records.

5. Missing or Incorrect SPF/DKIM Records

Some receiving servers reject email from domains that do not have SPF or DKIM authentication set up. This is increasingly common as providers tighten security.

Fix: Set up SPF and DKIM records in your domain's DNS. If you are not sure how, your email provider or hosting company should have documentation. Our deliverability guide covers this in detail.

6. Message Too Large

Most email servers have a maximum message size, typically between 10 MB and 25 MB including attachments. If your message exceeds this limit, it will bounce.

Fix: Reduce attachment sizes, compress files, or use a file-sharing service (Google Drive, Dropbox, etc.) and include a link instead.

7. Recipient Server Is Down

If the receiving server is temporarily offline, your server will usually retry delivery automatically for a period (often 24 to 72 hours) before giving up and sending a bounce. You may not even notice this happening.

Fix: Wait. If it is still bouncing after 24 hours, the problem is likely more than temporary.

8. Content Rejected by Spam Filters

Some servers reject emails based on content: too many links, suspicious keywords, or attachments with certain file extensions (.exe, .bat, .zip). You will see a 554 or 5.7.1 code.

Fix: Simplify your email. Remove excessive links, avoid spam-trigger words, and do not attach executable files. If you are sending a legitimate business email, try sending a shorter version without attachments to test.

What to Do About Persistent Bounces

If an address consistently bounces, stop trying after two or three attempts. Continuing to send to non-existent addresses hurts your sender reputation, which can cause deliverability problems for all your other emails.

For mailing lists and newsletters, remove hard-bounced addresses immediately. For soft bounces, most email marketing platforms will retry automatically and remove the address after several consecutive failures.

How Cleanbox Relay Handles Bounces

If you use Cleanbox Relay for inbound email routing, temporary bounces are handled automatically. When a destination server returns a 4xx code, Relay queues the message and retries delivery with exponential backoff — spacing out retries over increasing intervals to avoid overwhelming the destination server while maximizing the chance of eventual delivery. You do not need to monitor or manage this manually.

For permanent bounces (5xx), Relay immediately returns the failure to the sending server so the original sender knows their message was not delivered. No guessing, no delayed notifications.

Understanding bounce messages is one of those unglamorous but genuinely useful skills. Once you know how to read the status codes, most email delivery problems become straightforward to diagnose and fix.