From time to time you send an e-mail using your conventional e-mail client and, suddenly, you get a bounced e-mail as a response.
For example, take this one that I received today in my Outlook inbox:

What people usually do is just ignore and delete this kind of messages, but you should not do that. They contain very interesting information about the causes that lead to it, so you can know why the email get bounced and if this is a temporary or permanent failure among other things. You should look for this information in the body of the message (like in the previous image, surrounded by a red line) or in an attached text file.
The status code always consists in three numbers. They are standard SMTP codes defined under the RFC 1893 document.
As you can check by yourself in that document, for example, my bounced e-mail indicates a 5.1.1 status code, which means the following:
· 5: Permanent Failure
· 1: Addressing status (that’s is, something related to the address)
· 1: Bad destination mailbox address
So, obviously, it's an address that does not exist, although we already know that just looking at the "User unkown" sentence just after it. However not every email server in the Internet behaves in this same standards-compliant way.
Some SMTP servers return codes not totally compliant to the standard RFC and sometimes cause strange errors that can led to confusion. For example, a few days ago I receive a bounced mail with a status of 4.0.0. If you check the RFC you get this meaning for the code:
· 4: Persistent Transient Failure
· 0: Undefined Status (it does not give information about the problem)
· 0: Other undefined Status
So actuality it says nothing at all about the cause, and no SMTP server should return a 4.0.0 code, but there are several of them out there that wrongly do this. For example I checked the full status message for the bounced address and got this response from the server:
4.0.0: user over quota
Hey, that's just a crowded inbox, as long as we trust the returned message. But according to the RFC this situation should be it indicated by the standard status 4.2.2 which means specifically that the mailbox is full or over-quota.
I checked other server that returned other "strange" 4.5.2. code, and I got the following message:
4.5.2: Recipient address rejected: user over quota
Which is a totally wrong code because the meaning of this 4.5.2 is something related to the protocol, no t related to problems with the mailbox:
· 4: Persistent Transient Failure
· 5: Mail Delivery Protocol Status
· 2: Syntax error
Which is a crazy behavior from the mail server.
Normally you should not get 4.0.0 status codes, but if you do normally they are received from very unprofessional emails services, and normally they mean that the address does not exist. Our MAILCast service automatically handle and interpret all this bounced emails, and shows you a classified list of them that you can even export to Excel to do further processing on your own:

Besides the e-mail address that bounced and a short explanation, there is the received status code too (when is a hard bounce), so that you can check its meaning by yourself. We have studied a lot of oddities like the one I describe here to try to guess the real status of misbehaved servers, but it's virtually impossible to have them all correctly interpreted as long as some servers behave in a non-standard way. We're pretty accurate but, when in doubt, you know can see for yourself the meaning of any specific bounced email.
Just check the code in the RFC link above. It's easy!