How to Handle Bounced Emails as a Small Business: Read, Fix, Resend

A bounce is not a mystery; it is a report from the receiving server that says why delivery failed. Most business owners delete it and try again, which is the one thing that makes some bounces worse. This guide shows how to read the bounce in thirty seconds, what the common codes mean, and the right fix for each before you resend.

Quick summary

• 5xx is permanent: the message will not be delivered as sent. 4xx is temporary: your server keeps retrying for a day or two, and you usually receive a "delayed" notice first and a final bounce later if it never succeeds.
• 550 5.1.1 user unknown, "no such user", "address rejected": the address does not exist. Usually a typo or a person who left.
• 552 or 5.2.2 mailbox full, "over quota": the recipient's mailbox is full. Try again in a few days or reach them another way.
• 550 5.7.1 blocked, "message rejected due to spam", "policy": the receiver rejected your content or your domain's reputation or authentication. Check SPF, DKIM and DMARC before resending.
• 552 5.3.4 message too large: the attachment exceeds their limit. Send a link.

Step 1: find the reason line

Open the bounce (usually from Mail Delivery Subsystem, mailer-daemon or postmaster). Scroll past the boilerplate to a line that starts with a three-digit code such as 550 or 421, often followed by an enhanced code like 5.1.1 and a sentence. That line was written by the receiving server, and it is the diagnosis. Everything else in the bounce is padding. If your host keeps delivery logs, the same response is there: OquMail records each attempt with the remote server's exact reply.

Step 2: read the code

• 5xx is permanent: the message will not be delivered as sent. 4xx is temporary: your server keeps retrying for a day or two, and you usually receive a "delayed" notice first and a final bounce later if it never succeeds.
• 550 5.1.1 user unknown, "no such user", "address rejected": the address does not exist. Usually a typo or a person who left.
• 552 or 5.2.2 mailbox full, "over quota": the recipient's mailbox is full. Try again in a few days or reach them another way.
• 550 5.7.1 blocked, "message rejected due to spam", "policy": the receiver rejected your content or your domain's reputation or authentication. Check SPF, DKIM and DMARC before resending.
• 552 5.3.4 message too large: the attachment exceeds their limit. Send a link.
• 421 or 451 "try again later", "greylisted", "rate limited": temporary; do nothing, your server retries.
• Domain not found, "no MX records (the settings that tell the internet where to deliver email for your domain)": the domain in the address is wrong or the recipient's DNS is broken. Check the spelling.

Step 3: fix, then resend once

1. Typo: correct the address, update your contacts, resend. Do not resend to the wrong address again.
2. Left the company: find the successor through the company's main address or website. Delete the old address from every list.
3. Mailbox full: wait 48 hours, then resend once. If it bounces again, call.
4. Spam or policy block: run your own mail through a Gmail header check (Show original) and fix any SPF, DKIM or DMARC failure first. Remove anything spammy from the message (link shorteners, image-only body). Resend once. If blocked again, ask the recipient to whitelist your domain.
5. Too large: replace the attachment with a link and resend.
6. Temporary codes: do not resend. Your server already is. Resending creates duplicates when the retry succeeds.

Protect your reputation

• Never keep sending to an address that hard-bounced. Receivers count repeated attempts to dead addresses as a spam signal against your whole domain.
• Clean lists before a bulk send. If more than a few percent of a list bounces, stop and fix the list before continuing.
• Send bulk mail through a proper tool or an API that records bounces per message, rather than BCC from a mailbox.
• Keep your own DNS correct so receivers have no policy reason to reject you. OquMail's guided SPF/DKIM/DMARC setup removes the most common self-inflicted cause.

Bounces you did not send

A flood of bounces for messages you never wrote means someone is forging your address (backscatter). Check the bounced message inside the report: if the content is not yours and the originating Received line is not your host, it is forgery. The fix is a DMARC policy of quarantine or reject, which tells receivers to discard forged mail instead of bouncing it back to you.

Common questions

My message bounced but the address is definitely correct. Why?

Read the code. A correct address can bounce for mailbox full, policy block, size or a temporary error on their side. If it says user unknown, the address may be correct but the mailbox was deleted or their domain moved hosts without recreating it.

How long does a temporary bounce keep retrying?

Most sending servers retry for one to five days with increasing gaps, then give up and send a final bounce. A "delivery delayed" notice means the retrying is in progress and no action is needed.

Should I tell the recipient their mail bounced?

If you have another channel and the message matters, yes. A quick phone call or text saying "my email to you bounced, can you check your mailbox" is common and appreciated, and it often reveals a full mailbox or a changed address.