400/500 Email Bounce Back Errors Explained

Bounce backs and error codes for email can be very mysterious and misleading. To help with that we have started a new series on the blog dedicated to demystifying these occurrences. To read all of the blogs in this series, go here.

Bounce backs and error codes might look like they need to be deciphered with a secret decoder ring. We are going to try here to shed some light on them so you can crack them open and extract the goodness within. So let’s work together to understand the the two most common types of bounce backs. When a bounce back message is generated, the mail server that issued it is attempting to let you know there was a problem with sending the message and give you some information so you have an idea of what went wrong.

We are going to first break bounce backs into two main categories. Every bounce message will include a three digit number which is it’s “reply code”. This is different from the series of numbers, usually three, separated by periods. The reply code is defined by the SMTP protocol.  These other error codes are defined by specific mail server software packages and configurations and can be unique to each vendor.

The three digit reply code will either start with a 4 or a 5. These are commonly referred to as 400’s and 500’s as a group.

Basically if the number starts with a 4 it means the message delivery is having a temporary issue and will be delayed – these are called deferrals. If the message starts with a 5 then the message failed and was not sent to the recipient – these are called fatal message errors.

Deferrals (400)
A 400 bounce back indicates that there has been a delay or issue in sending your message. When this type of bounce back is sent to you, it means that your mail server will attempt to retry to send the message. If the retries are unsuccessful, the mail server will eventually stop trying to send the message after a specified amount of time. This amount of time is dictated by your server administrator but the typical time frame is a few days. If you don’t receive another bounce back it usually indicates that your message was able to be sent after a few tries and/or the issue was resolved. If you receive a fatal bounce back (500 error), it does mean that the message failed.

Fatal Bounce Back (500)
If the issue could not be resolved or there is another type of problem you may receive a 500 error. If the bounce back includes a 500 number, this means that the message was not delivered due to an error. The errors can vary across the board but typically it is an issue with one of the following: the email itself (misspelling, mailbox is full, etc.), your rDNS is not configured correctly, your server may be Blacklisted, or the message was blocked by the recipient spam filters due to content, attachment or a virus.

Remember that knowledge is power!  We at MxToolBox are constantly educating ourselves about all the different bounce backs that exist.  Also keep in mind that with some Vendors and ISPs you have the ability to create custom bounce back errors…so you always have to be on your toes!

If you are concerned about mail delays or other performance issues with your server we would highly recommend trying our Premium MailFlow Monitoring. This service sends a message through your server and back to our datacenter. This unique method allows us to provide complete mail flow visibility on your server. This can help uncover issues that might be creating delays as well as detecting both inbound or outbound mailflow failures.

In addition to alerts for failure, you can login to see daily, weekly and/or monthly historical statistics. This method allows you to get a true picture of the performance of your mail server.

Footnotes:
http://en.wikipedia.org/wiki/Non_delivery_report
http://tools.ietf.org/html/rfc821#page-35 – List of Reply Codes
http://tools.ietf.org/html/rfc821#page-48 – Theory of Reply Codes

One thought on “400/500 Email Bounce Back Errors Explained

  1. Johnny

    I am a Consultant and I am going to send this article to all of my clients so that they can learn to read errors on their own. It was helpful for me as well!

    Like

    Reply

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s