5.0.0
Other undefined Status
Undefined Status
2.0.1
Message delivered
The message was successfully delivered to the final recipient.
2.0.2
Message relayed
Unfortunately, the remote mail system does not support confirmation of
actual delivery. Unless the final delivery fails, this will be the only
delivery status notification sent.
5.1.0
Other address status
Something about the address specified in the message caused this DSN.
5.1.1
Bad destination mailbox address
The mailbox specified in the address does not exist.
This means the address portion to the left of the @ sign is invalid.
5.1.2
Bad destination domain address
The destination domain specified in the address does not exist or is
incapable of accepting mail.
This means the address portion to the right of the @ is invalid.
5.1.3
Bad destination mailbox address syntax
The destination address was syntactically invalid.
5.1.4
Destination mailbox address ambiguous
The mailbox address as specified matches one or more recipients on
the destination system. This may result if a heuristic address
mapping algorithm is used to map the specified address to a local
mailbox name.
5.1.5
Destination address valid
This mailbox address as specified was valid.
5.1.6
Destination mailbox has moved
The mailbox address provided was at one time valid but mail is no
longer being accepted for that address.
5.1.7
Bad sender's mailbox address syntax
The sender's address was syntactically invalid.
5.1.8
Bad sender's system address
The sender's system specified in the address does not exist or is
incapable of accepting return mail.
This means the address portion to the right of the @ is invalid.
5.2.0
Other or undefined mailbox status
The mailbox exists but something about the destination mailbox has
caused the sending of this DSN.
5.2.1
Mailbox exists but is disabled
The mailbox exists but is not accepting messages.
This may be a permanent error if the mailbox will never be re-enabled or
a transient error if the mailbox is only temporarily disabled.
5.2.2
Mailbox full
The mailbox is full because the user has exceeded a per-mailbox
administrative quota or physical capacity.
5.2.3
Message length exceeds administrative limit
A per-mailbox administrative message length limit has been exceeded.
5.2.4
Mailing list expansion problem
The mailbox is a mailing list address and the mailing list was unable
to be expanded.
5.3.0
Other or undefined mail system status
The destination system exists and normally accepts mail but
something about the system has caused the generation of this DSN.
5.3.1
Mail system full
Mail system storage has been exceeded.
5.3.2
System not accepting network messages
The host on which the mailbox is resident is not accepting messages.
Examples of such conditions include an immanent shutdown, excessive
load or system maintenance.
5.3.3
System not capable of selected features
Selected features specified for the message are not supported by the
destination system. This can occur when features from one domain cannot
be mapped onto the supported feature in another.
5.3.4
Message size exceeded
The message size exceeds the limit and therefore the message
was not delivered to the recipient.
5.3.5
System incorrectly configured
The system is not configured in a manner which will permit it to
accept this message.
5.4.0
Other or undefined network or routing status
Something went wrong with the networking but it is not clear what
the problem is or the problem cannot be well expressed with any of
the other provided detail codes.
5.4.1
No answer from host
The outbound connection attempt was not answered either because the
remote system was busy or otherwise unable to take a call.
5.4.2
Bad connection
The outbound connection was established but was otherwise unable to
complete the message transaction either because of time-out or
inadequate connection quality.
5.4.3
Name server failure
The network system was unable to forward the message because a
name server was unavailable.
5.4.4
Unable to route
The mail system was unable to determine the next hop for the message
because the necessary routing information was unavailable from the name
server. This means the address portion to the right of the @ is
currently invalid but may be valid in the future.
5.4.5
Mail system congestion
The mail system was unable to deliver the message because the mail
system was congested.
5.4.6
Routing loop detected
A routing loop caused the message to be forwarded too many times
either because of incorrect routing tables or a user forwarding loop.
5.4.7
Delivery time expired
The message was considered too old by the rejecting system either
because it remained on that host too long or because the time-to-live
value specified by the sender of the message was exceeded.
5.5.0
Other or undefined protocol status
Something was wrong with the protocol necessary to deliver the
message to the next hop and the problem cannot be well expressed with
any of the other provided detail codes.
5.5.1
Invalid command
A mail transaction protocol command was issued which was either out
of sequence or unsupported.
5.5.2
Syntax error
A mail transaction protocol command was issued which could not be
interpreted either because the syntax was wrong or the command is
unrecognized.
5.5.3
Too many recipients
More recipients were specified for the message than could have been
delivered by the protocol.
5.5.4
Invalid command arguments
A valid mail transaction protocol command was issued with invalid
arguments either because the arguments were out of range or
represented unrecognized features.
5.5.5
Wrong protocol version
A protocol version mis-match existed which could not be automatically
resolved by the communicating parties.
5.6.0
Other or undefined media error
Something about the content of a message caused it to be considered
undeliverable and the problem cannot be well expressed with any of
the other provided detail codes.
5.6.1
Media not supported
The media of the message is not supported by either the delivery
protocol or the next system in the forwarding path.
5.6.2
Conversion required and prohibited
The content of the message must be converted before it can be
delivered and such conversion is not permitted.
5.6.3
Conversion required but not supported
The message content must be converted to be forwarded but such
conversion is not possible or is not practical by a host in the
forwarding path.
5.6.4
Conversion with loss performed
This is a warning sent to the sender when message delivery was
successfully but when the delivery required a conversion in which
some data was lost.
5.6.5
Conversion Failed
A conversion was required but was unsuccessful. This may be useful
as a permanent or persistent temporary notification.
5.7.0
Other or undefined security status
Something related to security caused the message to be returned and
the problem cannot be well expressed with any of the other provided
detail codes.
5.7.1
Delivery not authorized
The sender is not authorized to send to the destination.
This can be the result of per-host or per-recipient filtering.
5.7.2
Mailing list expansion prohibited
The sender is not authorized to send a message to the intended mailing list.
5.7.3
Security conversion required but not possible
A conversion from one secure messaging protocol to another was
required for delivery and such conversion was not possible.
5.7.4
Security features not supported
A message contained security features such as secure authentication
which could not be supported on the delivery protocol.
5.7.5
Cryptographic failure
A transport system otherwise authorized to validate or decrypt a message
in transport was unable to do so because necessary information such as
key was not available or such information was invalid.
5.7.6
Cryptographic algorithm not supported
A transport system otherwise authorized to validate or decrypt a message
was unable to do so because the necessary algorithm was not supported.
5.7.7
Message integrity failure
A transport system otherwise authorized to validate a message was
unable to do so because the message was corrupted or altered.
5.9.1
Virus infection
One of the attachment(s) in the message is possibly infected by a virus.
For security reasons the message was not delivered to the recipient.
5.9.2
Virus infection
One of the attachment(s) in the message is possibly infected by a virus.
5.9.3
MAPS warning
The message was received by a host that is currently on the
MAPS list. Most likely the message is spam mail.
More information on MAPS ( Mail Abuse Protection System )
is avilable at
http://www.mail-abuse.org5.9.4
Spam SLS/RBL
The message was received from a host that is on a spam list.
5.9.5
Blocked attachment
One of the attachment(s) in the message is blocked.
For security reasons the message was not or not completely delivered to
the recipient.
5.9.6
Blocked subject
The subject of the message is blocked.
For security reasons the message was not delivered to the recipient.
5.9.7
Blocked message
One of the words in the message is blocked.
For security reasons the message was not delivered to the recipient.
5.9.8
Spam
The message seems to be spam and was not delivered to the recipient.