Email bounces happen from time to time, but high bounce rates can put your sender reputation in jeopardy, restricting the number of emails you can send to your audiences.
Further harming email deliverability is the possibility of being blacklisted if you have many hard bounces. Once you’re on email blacklists, you will have to fight tooth-and-nail to get off ’em. It’s doable but difficult.
Familiarizing yourself with email bounce codes will go a long way toward helping you understand why your messages bounce so you can reduce your bounce rates.
This is a detailed article, but it’ll still take less than 10 minutes to read. In this little guide, we will explain how to manage email bounce codes, and share a full list of email bounce codes and what they stand for.
Table of Contents
What Is an Email Bounce?
Let’s take it from the top and briefly explain what it means when an email bounces. A bounced email is any email that has not reached the recipient. The internet service provider or ISP returns it to you, which will happen instantly after you send it.
Depending on the cause of the bounce, you can try again later, recheck the recipient’s details, and send again immediately, or contact a different email address.
Bounces can be categorized in two ways: hard or soft. Let’s review the differences.
Soft Bounce vs Hard Bounce
A soft email bounce is often a temporary error caused by the recipient or their server, not the sender. Here are some reasons you might get a soft bounce when you email a segment of your contact list:
- Their email server can’t relay the message from your email server.
- The recipient’s email server requirements aren’t met.
- The email doesn’t pass the antivirus of the recipient server.
- The email got caught in the recipient’s spam filter.
- The email didn’t pass the recipient server’s authentication requirements, such as DMARC.
- The message violates the recipient server’s email policies.
- The recipient’s server blocks the content in the email.
- The recipient’s domain name no longer exists.
- The email is too big, usually due to attachments.
- The recipient server cannot receive emails due to sending out too many.
- The recipient’s server is offline.
- The recipient’s server is down.
- The recipient’s mailbox is incorrectly configured.
- The recipient’s mailbox is full.
The recipient doesn’t receive an email that your message to them bounced, so it’s up to them to improve matters on their end (or their ISP to do it, depending on the source of the soft bounce).
The other type of email bounce is a hard bounce. If soft bounces are temporary, hard bounces are permanent. For example, the recipient’s server might have blocked your email address. The email address you’re trying to reach might no longer exist, or you’ve contacted an invalid domain name.
Unlike a soft bounce, which the email recipient or their ISP might ameliorate in due time, there’s usually no return from a hard bounce. You can check the recipient’s email address and confirm you have everything spelled correctly, but you must remove them from your list outside of that.
You can calculate your soft vs hard bounces through your email bounce rate, which is the number of emails bounced divided by how many you sent.
A good bounce rate is around one percent (1%).
Okay, So What’s an Email Bounce Code?
Every email bounce, whether soft or hard, generates an email bounce code.
The bounce code explains why your email didn’t reach the intended recipient. You can receive a regular bounce code or an enhanced SMTP bounce code, which can be very different.
Traditional and Enhanced SMTP Bounce Codes – What’s the Difference?
SMTP is short for Simple Mail Transfer Protocol. All email servers use an SMTP to relay, send, and receive emails. A traditional SMTP bounce code will have a three-digit identifier indicating whether the email was sent.
The three-digit code tells you precisely why the email failed to reach the recipient, provided you understand what the code means.
In 2003, enhanced SMTP bounce codes were born. Traditional SMTP codes were helpful but only revealed so much, while the enhanced codes shed much more light on the matter. An enhanced SMTP code also has three digits but periods in between them.
What does each of the three digits mean? The first represents the email delivery class. A 2.X.X refers to a delivery that reached the recipient. If you see a 4.X.X, that indicates a soft bounce or a temporary issue. A 5.X.X is a hard bounce due to a permanent issue.
To recap, the first digit of an enhanced SMTP code can be a 2, 4, or 5.
The second digit represents an error code. If you see a 1 in the second spot, your email didn’t send because of an address issue. A 2 represents a mailbox problem, and a 3 means it’s an issue with the mail server.
The second digit of an enhanced SMTP code can be a 1, 2, or 3. Then, there’s the third digit, which further elaborates on the email issue. This can be between 0 and 5.
ISPs use traditional and enhanced SMTP codes to help email senders understand why their messages failed.
Read also: Bounce Back Emails: What Are They And How To Fix Them
Understanding Email Bounce Codes: The Full List and What They Mean
Let’s put all the information together from the prior section and review the common bounce codes and what they mean when you receive them.
Status Group Codes
A status group code refers to the first of the three digits in an enhanced SMTP code and is as follows.
Status Group Code | What It Means |
1XX | Informational group indicating the server received and is still processing your request. |
2XX | The server successfully got your request and has accepted it. |
3XX | Redirection group indicating that the server must do more to fulfill the request. |
4XX | Client error indicating the server could not fulfill the request, or it has bad syntax. |
5XX | Server error indicating the server couldn’t fulfill the request but not due to any errors on the sender’s part. |
4XX Codes
Soft bounce codes begin with 4, such as 4XX (a traditional SMTP bounce code) or 4.X.X (an enhanced SMTP bounce code). Here’s an overview of each code and its meaning.
Code | What It Means |
420 | An error occurred when transferring the message, and the connection timed out. |
421 | The recipient’s server cannot receive the message because of excess connections or messages. The email is deferred until the recipient can receive messages again. |
422 | The recipient’s inbox is full and has no storage space left. |
431 | The recipient has a file overload and is out of memory or disk space. |
432 | The arriving mail queue was stopped due to the exchange server. |
441 | The recipient’s server has stopped responding. |
442 | The recipient’s server lost connection while the transmission occurred. |
446 | The recipient has exceeded their email hop count and caused an internal loop error. |
447 | The incoming server had an issue, causing the email you sent to time out. |
449 | Routing issues, possibly caused by configuration trouble, prevented the server exchange. |
450 | The mailbox is busy or otherwise unavailable. |
451 | The message could not be processed and was aborted. |
452 | The system lacks enough storage to send the email. |
471 | A local anti-spam filter prevented the email from going through. |
5XX Codes
Hard bounce codes begin with a 5, either a 5XX or a 5.X.X. Here is a complete overview of all the codes you might receive when a permanent error occurs during email sending.
Code | What It Means |
500 | The email address doesn’t exist. |
501 | Command arguments encountered a syntax error. |
502 | The server cannot implement the requested command. |
503 | A sequence of commands has prevented the server from proceeding. |
504 | The recipient could not implement the command parameter. |
510 | You’re trying to reach a bad or invalid email address. |
511 | You’re trying to reach a bad or invalid destination. |
512 | The recipient’s server had a DNS error and could not find the domain name for the recipient. |
513 | An address has been misspelled or cannot be authenticated. |
514 | The recipient’s mailbox address is deemed ambiguous, and cannot receive the message. |
515 | The mailbox address is invalid. |
516 | The mailbox has moved. |
517 | A bad mailbox address syntax has prevented the recipient’s server from receiving your message. |
518 | A bad system address has prevented the recipient’s server from receiving your message. |
520 | The recipient’s mailbox status is undefined. |
521 | The recipient’s mailbox is no longer accepting messages due to being disabled. |
522 | The recipient’s mailbox is full, and they can no longer receive messages until they empty it. |
523 | You’re trying to send an email that exceeds the limits of the recipient’s server. |
524 | The mailing list could not be expanded. |
530 | The recipient’s email address is invalid, the recipient’s server blacklisted your email address, or authentication issues. |
532 | The system cannot accept network messages. |
533 | The system cannot accept some selected features. |
534 | The size of the message exceeds the allowable system size. |
540 | The routing status or network is undefined. |
541 | An anti-spam filter or other measure rejected the message by recipient address. |
542 | Poor connection. |
543 | The routing server failed. |
544 | The server cannot route. |
545 | The network is congested. |
546 | The network detected a routing loop. |
547 | The period for delivery expired. |
550 | The server could not find the recipient’s mailbox. |
551 | The recipient isn’t a local part of the server. |
552 | The storage allocation was exceeded, and the request was aborted. |
553 | The mailbox name was invalid, and the request was aborted. |
554 | The email transaction failed, although for reasons not stated. |
555 | The protocol version is incorrect. |
560 | A media error occurred. |
561 | The type of media sent is not supported. |
562 | The required conversion is prohibited. |
563 | The required conversion is not supported. |
564 | The conversion occurred but with a loss. |
565 | The conversion could not occur. |
570 | The security status is undefined. |
571 | The message was refused due to unauthorized delivery. |
572 | The server prohibited mailing list expansion. |
573 | The required security conversion could not occur. |
574 | The required security conversion is not supported. |
575 | A cryptographic error or failure occurred. |
576 | The required cryptographic algorithm isn’t supported. |
577 | The message integrity failed. |
Read also: Bounce Rates and Email Deliverability – A Simple Guide
How To Manage Email Bounce Codes
Bounced emails put your sender reputation at risk if they happen frequently enough, including hard and soft bounces alike.
Although you can’t control what your email recipients do or how their server behaves, you have plenty within your power to reduce your company’s email bounce rate.
Here are some pointers.
Pause emails to the recipient
You’ve determined the intended recipient cannot accept emails at current, likely due to a temporary issue. Check the bounce code; if you see a code beginning with a 4, it’s a soft bounce that should be rectified when possible.
In the interim, it does no good to continue sending emails, as they will all bounce. Instead, temporarily pause emails to that recipient. A pause might mean 24 or 48 hours or even a week. It’s your choice how long you decide to wait.
Try sending the email again and decide how to proceed based on whether you get the same error, a different error, or no error.
Read also: Email List Cleaning – It’s Time To Give Yours A Good Scrub
Remove inactive email addresses
If you’re still receiving 4XX or 4.X.X email bounces from the recipient, despite a temporary bounce, that doesn’t mean it will always be addressed. Soft bounces are on the part of the recipient, such as a full email inbox.
You don’t want to hold your breath waiting for the email recipient to empty their inbox, as you don’t have any way of knowing how long you’ll wait. Instead, remove them (and any other inactive addresses) from your email list.
If the recipient gets their email issues fixed and realizes they aren’t receiving your emails, they can sign up for your email list again. In the meantime, keeping them on your list could put you at risk of your ISP assuming you’re engaging with spam traps, thus hurting your sender reputation.
If you’ve received a 5XX or 5.X.X email bounce, remove the recipient immediately. These permanent issues are highly unlikely to be fixed.
Validate email addresses
Do you validate your emails before sending them? This is a great way to reduce the amount that will bounce. You can use free email verification through some services, so even startups can begin validating email addresses.
Read also: 29 Critical SMTP Response Codes And How To Fix Them
Use double opt-ins
People accidentally end up on email lists all the time, whether a company unscrupulously sold their email address as part of a list sale or they signed up and completely forgot.
Instituting double opt-ins during signup reduces the rate of unintended signups, no matter the reason. You’ll improve your open and click-through rates and reduce your bounce rate.
Follow good email hygiene
Double opt-ins are one part of proper email hygiene, which means following best practices to maintain your sender reputation.
Here is a list of behaviors to begin implementing if you aren’t already.
- Do not use spam words in your subject lines or email bodies.
- Don’t mislead or lie to your audience in the subject line.
- Make it simple for anyone to unsubscribe, so if they’ve changed their minds or no longer want to be part of your email list, they can very easily exit.
- Keep your email list full of engaged subscribers, removing inactive emails that bounce.
- Find an email cadence that works for your audience. Perhaps you email them once or twice a week, or maybe every few days, but it should be a rate most of your customers find agreeable.
- Optimize your emails for mobile and desktop users.
- Segment your audience.
- Personalize your emails.
- A/B test your emails before sending them.
- Ensure your hyperlinks and CTAs are clear about where they’ll redirect the user.
- Don’t use spammy practices in the preview text.
- Never attach anything to your emails unless the user already knows about it.
- Do not write overly long emails.
- Always send emails from the same server and address.
- Send welcome emails to all new subscribers, and without delay.
Watch your sending limits
Do you use a free email server? Many of them institute send limits.
For example, Gmail only allows paid users to send 2,000 emails daily, and it’s 500 if you have a free account. You can go through that number of emails fast as a large corporation, but all emails over the limit will bounce.
Consider moving to your own server with greater limits. This will also build trust and credibility. However, you can warm up your IP by gradually increasing your volume of emails before you launch an email blast.
If you don’t, your ISP will likely block your messages.
Read also: ISP and Email Deliverability: How To Hit The Inbox Always
Bottom Line
Email bounce codes are broadly categorized by soft and hard bounces. The codes reveal what went wrong so you can remedy the issue, even if that’s merely by pruning your email list.
If you want help with your email marketing, try EngageBay for free. Thousands of small business owners love this tool, and it comes with integrated CRM & helpdesk solutions.