You send a quotation to a customer, and a few minutes later your inbox shows a message from a system address with a subject such as “Delivery Status Notification (Failure)” or “Undelivered Mail Returned to Sender”. It is long, it is full of codes, and it does not say what to do. This guide is for an owner or office manager who sends business email from an address on their own domain. It shows how to read any bounce in about a minute, what the status code families mean in plain words, which common causes you can fix yourself and which only the recipient or your host can fix, and what to send to support when you need help. Mail services word their bounces differently and change them over time, so use this as a reading method, not a dictionary.
What a bounce is and where it arrives
A bounce, formally a delivery status notification, is an automatic message from a mail system saying it could not deliver your email. It arrives in the inbox of the address you sent from, usually from a system sender such as a mail delivery system or a mailer address, and usually quotes your original subject. It can come back within seconds, or hours or days later, because a mail system sometimes keeps trying before it gives up.
Two kinds exist, and the difference matters. A failure notice says the system has stopped trying: the message was not delivered. A delay notice says delivery has not worked yet but the system is still trying, so no action is needed unless it ends in a failure. The wording near the top, such as “could not be delivered” or “delayed”, usually tells you which one you have.
The three parts to read
Ignore the length. Almost every bounce comes down to three things, and you can find them in any of them.
| Part | What it tells you | Where to look |
|---|---|---|
| The address that failed | Which recipient was not reached. One address failing while others worked points to that recipient; every address failing points to your side. | Near the top, often after words such as “your message to” or a line named Final-Recipient. |
| The status code | Whether the problem is permanent or temporary, and the general area: address, mailbox, mail system, network, content or policy. | A short code such as 550 or 5.1.1, often on a line named Status or Diagnostic-Code. |
| The plain-text reason | What the system objected to, in words. This is the line to trust most. | The sentence next to the code, or the first paragraph of the notice. |
Many bounces also name the remote mail server that refused the message, and show the original message headers at the bottom. You rarely need those yourself, but your host or support can use them, which is why you keep the whole text.

A made-up bounce, read line by line
Here is an invented example using example.com style addresses. It is not copied from any real mail system, and real wording differs.
Subject: Delivery Status Notification (Failure) From: Mail Delivery System <[email protected]> Date: 18 Nov 2026 10:42 +0800 Your message to [email protected] could not be delivered. Final-Recipient: rfc822; [email protected] Action: failed Status: 5.1.1 Diagnostic-Code: smtp; 550 5.1.1 The email account that you tried to reach does not exist.
- Address that failed: [email protected]. Check it letter by letter against the address you meant to use.
- Action: failed: the system has stopped trying. A line reading “delayed” would mean it is still trying.
- Status 5.1.1 and 550: the leading 5 means permanent. The reason says the account does not exist.
- What to do: this is the typo or wrong-address case. Fix or confirm the address another way, then send once. Resending the same message to the same address will fail again.
Permanent or temporary: what the codes mean in plain words
Mail systems report two kinds of code. The three-digit reply code (such as 550 or 421) is the short answer given while the message is being handed over. The longer enhanced status code (such as 5.1.1 or 4.2.2) is written as three numbers separated by dots, and gives more detail. In both, the first digit carries the main message:
- Starts with 4: temporary. The receiving side could not take the message right now, for example because it is busy, the mailbox is briefly unavailable or the system is limiting how fast it receives mail. The sending system normally tries again, often for a period that can run to a few days depending on that system, and only then sends a failure. A single temporary notice usually needs no action.
- Starts with 5: permanent. The message was refused and will not be retried. Sending the same thing again does not help until the cause is fixed.
The middle number of the enhanced code points to the general area. As a rule of thumb: 1 is about the address, 2 about the mailbox, 3 about the mail system, 4 about the network or routing, 5 about the delivery conversation between servers, 6 about the message content, and 7 about security or policy. So 5.1.1 is a permanent address problem, 4.2.2 is a temporary mailbox problem, and 5.7.1 is a permanent refusal on policy grounds. The industry documents behind these codes are public (RFC 3463 for the enhanced codes), and a mail service’s own help page is the place to confirm its wording. Codes are guidance, and the plain-text reason matters more.
The bounce-reading table
This table maps the common causes to what they usually look like and who can fix them. The codes shown are the ones commonly seen, not a promise: services differ, so match on the reason in words first.
| Cause | Often looks like | Commonly seen code | Who can fix it |
|---|---|---|---|
| Wrong address or typo | “address not found”, “user unknown”, “no such user” | 5.1.1 (550) | You, by correcting or confirming the address |
| Recipient mailbox does not exist or was closed | “account does not exist”, “mailbox unavailable”, “disabled” | 5.1.1 or 5.2.1 | The recipient. You can only reach them another way. |
| Recipient mailbox full | “mailbox full”, “over quota” | 5.2.2 (permanent) or 4.2.2 (temporary) | The recipient |
| Domain not found, or DNS or mail routing recently changed | “domain not found”, “host not found”, “unable to route”, “no mail server” | 5.1.2 or a 5.4.x code | You if it is a typo in the domain; the domain owner if the records are wrong |
| Message too large | “message too large”, “exceeds size limit” | 5.3.4 or 5.2.3 | You, by shrinking or sending a link |
| Blocked or rejected as spam, or by policy | “rejected”, “blocked”, “spam”, “policy”, “reputation” | 5.7.1 or another 5.7.x | Partly you; often the recipient’s administrator |
| Sender authentication failed at the receiver | Wording that mentions SPF, DKIM or DMARC, “not authenticated”, “unauthenticated” | 5.7.x | The owner of the sending domain’s DNS, with your host |
| Your own account blocked or over a sending limit | “too many messages”, “rate limit”, “account suspended”, “sending not allowed” | A 4.x.x or 5.x.x code | You and your host |
| Temporary “try again later” | “deferred”, “temporarily”, “try again later”, Action: delayed | 4.x.x | Usually nobody; it clears by itself |
If the wording fits more than one row, go by the plain-text reason, and when in doubt keep the whole bounce for support.
What to do for each cause
- Wrong address or typo. Compare the failed address with the one you were given, character by character. Look for a missing letter, .con instead of .com, or a mix-up between similar letters and digits. If you copied it from an old email, ask the person to confirm it by phone or message. Then send once.
- Mailbox does not exist or was closed. The address was valid once, or never was. People leave companies and mailboxes are closed. Ask the customer for a current address. Do not keep resending.
- Recipient mailbox full. You cannot clear their mailbox. Tell them another way, such as WhatsApp or a call, and try again later. If the full mailbox is your own, see our guide to a full business mailbox.
- Domain not found, or records recently changed. First check the spelling after the @. If the spelling is right and the address worked before, ask whether the recipient’s domain, website or email was recently moved or renewed, because wrong or missing DNS records stop mail finding its destination. If it is your own domain that changed, this is a DNS question for your host; see DNS explained in plain words for what the records do.
- Message too large. Shrink the files or send a link instead. The full walk-through is in our guide to email attachments that are too large, so it is not repeated here.
- Blocked or rejected as spam or by policy. Read the reason: it may say what was objected to, such as a link, an attachment type, a reputation problem or a missing authentication check. Remove anything that looks suspicious, avoid sending the identical message again, and try a plain text version. If it keeps happening to many recipients, treat it as a sender-side problem and ask for help. Do not try tricks to get round a filter.
- Authentication failed at the receiver. Receiving systems increasingly check that mail claiming to come from your domain really does. If a bounce mentions SPF, DKIM or DMARC, your domain’s DNS needs correct records. This guide cannot tell you what values to publish for your domain; ask your host or support what to publish, and see domain email versus free email for why it matters.
- Your own account blocked or over a sending limit. Hosts and mail services often limit how many messages an account can send in a period, and may pause an account that looks compromised or sends a burst. If several recipients bounce with wording about limits or about your account, stop sending and ask your host in writing. If you were sending to a list, read why bulk mail from a mailbox gets blocked. If the settings on your phone or laptop were changed recently, check them against business email on your phone and laptop.
- Temporary “try again later”. Do nothing at first. The sending system retries on its own. If a final failure arrives, or the same temporary notice repeats for the same recipient over a day or two, treat it as a keeps-bouncing case below.
A bounce that may not be real: do not click
Scammers imitate delivery failure notices because people open them. A fake one often claims your message or a document “could not be delivered” or “is on hold” and offers a button to “release”, “verify” or “sign in”. A genuine bounce is only an explanation: it never needs you to sign in or pay.
- Check you sent something. Open your Sent folder. A genuine bounce matches a message you recently sent, to an address you can recognise, and quotes its subject.
- Do not click links in an unexpected bounce. If you did not send anything, or the notice pushes you to click, sign in or pay, leave it alone.
- Look at the sender and the wording. Odd sender names, urgency, spelling mistakes and links that do not belong to a mail system are warning signs.
- When in doubt, check another way. Sign in to your mail service or control panel yourself by typing the address, never through a link in the notice, and ask your host if unsure.
The same habits apply to fake renewal and account notices; see how to recognise fake domain renewal emails. And if the problem is the opposite, a message that should have reached you but never produced any email at all, read why website enquiries may not reach your inbox.
Once, or keeps bouncing?
The pattern over a few tries tells you more than any single bounce. This table is a short decision aid.
| What you see | Most likely meaning | Do this |
|---|---|---|
| Bounced once, a 5 code, one recipient | A problem with that address or that recipient’s system | Check and fix the address, confirm it another way, send once. |
| Bounced once, a 4 code or “delayed” | A temporary condition | Wait. Keep the notice. Do not resend straight away. |
| Same recipient bounces again after a fix | The cause is not what you assumed, or it is at their end | Contact them another way and ask their IT to look. Send them the bounce text. |
| Many recipients bounce, or every message you send | Your account, your settings, your domain’s records or a block | Stop sending and ask your host in writing. Include the bounce text. |
| Only some large messages bounce | A size limit | Shrink or send a link. |
| Bounces started right after a change to your domain, hosting or email settings | The change, such as a record or a setting | Say what changed and when, and ask your host to check. |
| A notice asking you to click, sign in or pay | Possibly a fake | Do not click. Check your Sent folder and report it if unsure. |
When to ask support, and what to include
Ask for help when the same recipient keeps bouncing after you fixed the address, when many recipients bounce, when every message you send fails, or when the wording points to your own account, limits or authentication. A support person can do much more with the whole text than with a description.
- Copy the full bounce text. Paste it into the ticket from top to bottom, including the code, the reason line and any technical lines at the bottom. Never send only a screenshot: a screenshot cannot be searched, and the useful lines are often cut off.
- The time you sent it. Give the date, the time and your time zone, so the log can be found.
- Both addresses. The exact sender address you used and the exact recipient address that failed.
- What you were sending. The subject, whether it had an attachment and roughly how big, and whether you replied or started a new message.
- The pattern. How many times, how many recipients, whether other recipients work, and what changed recently.
- Do not send passwords. A ticket never needs your mailbox password.
A short template you can adapt: “On [date] at about [time] (MYT) I sent an email from [sender address] to [recipient address], subject [subject]. It bounced [number] time(s) with the message below. Other recipients [do / do not] work. The last change to my domain or email settings was [change and date]. Full bounce text: [paste].”
Common mistakes
- Resending without reading. A permanent failure fails every time, and repeated sends help nobody.
- Sending only a screenshot to support. The full text, including the code and the time, is what helps.
- Reading the subject line only. The same subject covers both temporary and permanent problems; the code and reason decide.
- Trusting the code over the words. Services use codes a little differently. Read the plain-text reason first.
- Assuming the recipient is at fault. If every message you send bounces, the cause is on your side.
- Clicking a link in an unexpected bounce. It may be a fake delivery notice.
- Ignoring a recent change. A new website, a domain renewal or a new mail setup is often the real cause of sudden bounces.
- Treating silence as delivered. Some failures never produce a bounce at all, so confirm anything important.
Where Gotka Technologies fits
Gotka runs cPanel hosting, and email accounts come with the plans: Go AI Lite includes 30 email accounts and Go AI Plus includes unlimited email. Gotka also offers domain registration from RM10/yr, so your email address can match your own domain.
This guide does not state how Gotka’s mail servers word bounces, how long they retry, how they queue mail, what sending limits apply, how spam is filtered or whether an address is on any blocklist, because none of that is published in the material it can cite. For your own account, send the full bounce text through the client-area ticket system, or call or WhatsApp +60 11-6331 6630, Monday to Friday, 9am to 6pm (MYT).
Key terms used in this guide
- Bounce: an automatic message saying an email was not delivered. Also called a delivery status notification or non-delivery report.
- Permanent failure: a refusal that will not be retried. Codes start with 5.
- Temporary failure: a problem that may clear by itself; the sender keeps trying for a while. Codes start with 4.
- Reply code: the three-digit answer a mail server gives during delivery, such as 550.
- Enhanced status code: a three-number code such as 5.1.1 that adds detail to the reply code.
- Mailbox full or over quota: the recipient’s mailbox has no room for more mail.
- MX record: a DNS record that says which server receives mail for a domain.
- DNS: the system that links a domain name to the servers behind it.
- SPF, DKIM and DMARC: checks that help a receiving system confirm mail really comes from the domain it claims.
- Rate limit: a cap on how many messages an account may send in a period.
- Phishing: a fake message designed to trick someone into clicking a link or giving up a password.
What does it mean when my email bounces?
It means a mail system could not deliver your message and sent you an automatic notice instead. The notice names the address that failed, a status code and a reason in plain text. Some bounces mean the message will never arrive until you fix something, and others only report a delay. Read the reason before you resend.
What is the difference between a 4xx and a 5xx bounce?
A code starting with 4 reports a temporary problem, and the sending system usually keeps retrying for a while. A code starting with 5 reports a permanent failure, so retrying the same message will not help until the cause is fixed. Services use codes a little differently, so treat them as guidance and trust the plain-text reason.
Why did only one recipient bounce when I sent to several people?
A bounce is reported for each address. If only one address failed, the cause is usually at that recipient: a typo, a mailbox that does not exist, a full mailbox or their own mail system refusing the message. If every address bounced, look at your side instead: your account, your sending settings or the message itself.
Should I keep resending a message that bounced?
Not until you know why. A permanent failure such as an address that does not exist will fail every time, and repeated sends can make your mail look worse. Fix the address or the cause first, then send once. A temporary failure may clear on its own, so wait a while and keep the bounce if it persists.
Is a “delivery failed” email always real?
No. Fake notices are a known phishing pattern. A real bounce refers to a message you sent recently to an address you can recognise. If you sent nothing, or the notice asks you to click a link, sign in or pay to release the message, do not click. Check your Sent folder and ignore it if it does not match.
What should I send support when my email keeps bouncing?
Send the full text of the bounce, not a screenshot alone, together with the time you sent the message, the sender address, the recipient address and what you were sending. Say how many times it failed and whether other recipients work. Gotka customers can use the client-area ticket system, which keeps the details in writing.
Does this guide say what Gotka’s mail servers write in a bounce?
No. It does not describe how Gotka’s mail servers word bounces, retry messages, limit sending or filter spam, because none of that is published in the material it can cite. If you need an answer for your own account, ask in writing through the client-area ticket system, or call or WhatsApp +60 11-6331 6630, Monday to Friday, 9am to 6pm (MYT).
Email Attachment Too Large? Why It Bounces and How to Send Big Files Without the Message Coming Back
Email attachment too large or bounced? Why size limits reject a message, how to read a message-too-large bounce, shrink files and send big files by link safely.
HostingBusiness Email on Your Own Domain: Why hello@yourcompany Beats a Gmail Address
Why hello@yourcompany beats a free Gmail address, why it's already included with Gotka hosting, and why SPF, DKIM and DMARC now decide if it reaches the inbox.
HostingBusiness Email on Your Phone and Laptop: IMAP vs POP, Outlook and the Gmail App
Set up business email on your phone and laptop: find the settings in cPanel, choose IMAP over POP, add it to Outlook, iPhone or Gmail, and fix sign-in errors.


