Detailed list of Email Statuscodes part 1
(More detailed explanation.)When you receive a delivery status/ DSN message, you will find an included report with the reason why the e-mail delayed or could not be delivered.
If your organization uses Microsoft Exchange, you'll very likely receive an NDR message.
Location of the reason inside the notification e-mail.
In the notification e-mail you'll first find an introductory text of the Mail Delivery System. About halfway you will find the extensive diagnostic information. It looks like this:Reporting-MTA: dns; mail.server.com
X-Postfix-Queue-ID: AAEEFF1234
X-Postfix-Sender: rfc822; sender@thesender.com
Arrival-Date: Tue, 24 Oct 2006 20:59:35 +0200 (CEST)
Final-Recipient: rfc822; receiver@thereceiver.com
Original-Recipient: rfc822;receiver@thereceiver.com
Action: failed
Status: 5.1.1
remote-MTA: dns; mail.thedestination.com
Diagnostic Code: smtp; 550 5.1.1. No such user
The rules of interest are the following:
Rule; Meaning
Reporting-MTA; This is the reporting server. Usually, the server that reports the, not the server where the problem actually arises.
Original-Recipient; The recipient of the original e-mail message.
Status: The status code that indicates why the original message could not be delivered. The status codes are described below.
Diagnostic Code; One more 'informal' description(s) why the original message could not be delivered. Frequently used descriptions are described below.
Status;
4.0.0
A temporary disturbance occurred while sending the e-mail. It could not be determined what the exact malfunction was. You should look at the text near the 'Diagnostic Code', it probably tells you the reason of the temporary disruption.
4.4.1
The receiving mail server does not respond. This code can be a result of temporary network problems. The mail server will automatically try to reconnect and deliver the e-mail. If the delivery after several attempts still has not been successful, a delivery status notification for a permanent malfunction will be generated.
4.4.2
The connection between the sending and receiving mail server is lost. This code can be a result from temporary network problems. The mail server will automatically try to reconnect and deliver the e-mail. If the delivery after several attempts still has not been successful, a delivery status notification for a permanent malfunction will be generated.
4.4.4
The sending mail server could not determine what receiving mail server is responsible for the destination domain. This indicates a configuration error in the DNS records of the destination domain.
4.4.6
The maximum number of hops for the message was exceeded. This code can also be generated if an infinite loop is created between the sending and receiving server that are not part of the same organization. The message is then sent back and forth until the maximum number of hops is exceeded.
5.0.0
A permanent malfunction occurred while sending the e-mail. The exact malfunction could not be determined. You should look at the text near the 'Diagnostic Code', it probably tells you the reason of the permanent disruption.
5.1.0
There is a non existing e-mail address or the e-mail address contains an invalid syntax.
5.1.1
The used e-mail address does not exist. The part left of '@' character (the so-called 'local part ") is not accepted by the receiving mail server.
5.1.2
The used e-mail address does not exist. The part right of '@' character (the so-called 'domain part ") is not accepted by the receiving mail server.
5.1.3
The e-mail address is not correct in terms of syntax and is therefore not accepted by the receiving mail server. This situation is usually caused when you use spaces in the e-mail addresses, or if a semicolon (;) is used to separate multiple e-mail addresses instead of a comma (,).
5.2.1
The receiving mail server recognizes the e-mail address, but the mail account of the user is disabled. You can best use an alternative e-mail address.
5.2.2
The receiving mail server recognizes the e-mail address, but the mailbox of the user is full. The e-mail is not received. The best is to use an alternative e-mail address or to try again later.
5.3.4
The message you sent is too large. Try to reduce the number of attachments, or compress the attachments.
5.4.4
The sending mail server could not determine what receiving mail server is responsible for the destination domain. This indicates a configuration error in the DNS records of the destination domain.
Diagnostic-Code;
Connect to mail.thedestination.com[127.0.0.1]: Operation timed out. The receiving mail server does not respond. This code can be a result of temporary network problems. The mail server will automatically try to reconnect and deliver the e-mail. If the delivery after several attempts has still not been successful, a delivery status notification for a permanent malfunction is generated.
Connect to mail.thedestination.com[127.0.0.1]: Connection refused. The receiving mail server does not respond. This code can be a result of temporary network problems. The mail server will automatically try to reconnect and deliver the e-mail. If the delivery after several attempts still has not been successful, a delivery status notification for a permanent malfunction will be generated.
Host or domain name not found. Name service error for name = thedestination.com type = MX: Host not found, try again The sending mail server could not determine what receiving mail server is responsible for the destination domain. This indicates a configuration error in the DNS records of the destination domain.
501 Bad Address Syntax
The e-mail address is not correct in terms of syntax and is therefore not accepted and ignored by the receiving mail server. This situation is usually caused when you use spaces in the e-mail addresses, or if a semicolon (;) is used to separate multiple e-mail addresses instead of a comma (,).
550 User unknown / No such user / Invalid user / Invalid alias / etc.
The used e-mail address does not exist. The part left of '@' character (the so-called 'local part ") is not accepted by the receiving mail server.
554 Relay access denied / We don't relay for .... / Etc. The used e-mail address does not exist. The part right of '@' character (the so-called 'domain part ") is not accepted by the receiving mail server.
Your IP
Your IP address: 107.21.156.140
Navigation
