SMTP error codes are generated for a variety of reasons. Server bounces can indicate a delay or a failure. It’s important to notice which you are dealing with. A delayed message will be re-tried until succeeded or timed out. A failure will not retry until the message is resent – doing so without resolving the issue will likely only result in another failure.

When someone outside your organization reports a bounce, knowing this information can help determine if the error is with the sender’s server, the message or address they are sending to, or if the problem is with our network.

Here is a breakdown of error codes:

• Codes that start with 0x800***** (where * is another digit (0-9) or letter (a-f)) are generally internal outlook errors, and may need to be researched.

• Codes that start with 4** (where * is another digit (0-9)) are “temporary” errors, these errors normally result in a delay in sending.

• Codes that start with a 5** (where * is another digit (0-9)) are permanent failures.

Here are some example error codes:

SMTP Error Examples

To enable us to help you resolve the issue, we need to know what type of error we are dealing with. If you have the bounce message, you can forward it to support if you are unable to read the reason for the error yourself.

If you have received a report of a bounce from an outside party, you will need to get this information from them. If they are unable to provide this information by email, you could suggest they print and fax the error to you for forwarding to us. 

server

SMTP

RTS