The population of data for the Bounce Count and Bad Address Date fields can be configured, for each SMTP response received from an email sent out of Association Anywhere/Certelligence.
There are two classes of SMTP responses that can be received from an email server. ECM SMTP Response Reply Codes and ECM SMTP Enhanced Status Codes.
Navigation: “Admin”> “Marketing & Communications” > “E-Communications” > “Bounceback Processing”
ECM SMTP Response Reply Codes
| Reply Code | Description | Increase Bounce Count | Mark as Bad |
|---|---|---|---|
| 101 | The server is unable to connect | Y | N |
| 111 | Connection refused or inability to open an SMTP stream | Y | N |
| 200 | (nonstandard success response, see rfc876) | N | N |
| 211 | System status, or system help reply | N | N |
| 214 | Help message | N | N |
| 220 | Service ready | N | N |
| 221 | Service closing transmission channel | N | N |
| 250 | Requested mail action okay, completed | N | N |
| 251 | User not local; will forward to | N | N |
| 252 | Cannot VRFY user, but will accept message and attempt delivery | N | N |
| 354 | Start mail input; end with CR LF.CR LF | Y | N |
| 355 | Octet-offset is the transaction offset | Y | N |
| 400 | Message delayed | Y | N |
| 403 | TLS handshake failed | Y | N |
| 420 | Timeout connection problem | Y | N |
| 421 | Service not available, closing transmission channel | Y | N |
| 422 | The recipient’s mailbox has exceeded its storage limit | Y | N |
| 431 | Not enough space on the disk | Y | N |
| 432 | Microsoft Exchange Server SMTP error code. Contact it to get more information | Y | N |
| 441 | The recipient’s server is not responding | Y | N |
| 442 | The connection was dropped during the transmission | Y | N |
| 446 | The maximum hop count was exceeded for the message: an internal loop has occurred | Y | N |
| 447 | Your outgoing message timed out because of issues concerning the incoming server | Y | N |
| 449 | Routing error: Microsoft exchange only | Y | N |
| 450 | Requested mail action not taken: mailbox unavailable | Y | N |
| 451 | Requested action aborted: local error in processing | Y | N |
| 452 | Requested action not taken: insufficient system storage | Y | N |
| 453 | No mail | Y | N |
| 454 | TLS not available due to temporary reason. Encryption required for requested authentication mechanism | Y | N |
| 458 | Unable to queue messages for node | Y | N |
| 459 | Node not allowed: reason | Y | N |
| 471 | An error of your mail server, often due to an issue of the local anti-spam filter | Y | N |
| 500 | Syntax error, command unrecognized | Y | N |
| 501 | Syntax error in parameters or arguments | Y | N |
| 502 | Command not implemented | Y | N |
| 503 | Bad sequence of commands | Y | N |
| 504 | Command parameter not implemented | Y | N |
| 510 | Bad email address | N | Y |
| 511 | Bad email address | N | Y |
| 512 | DNS error: the host server for the recipient’s domain name cannot be found | Y | N |
| 513 | Address type is incorrect | Y | N |
| 515 | Destination mailbox address invalid | Y | N |
| 517 | Problem with senders mail attribute, check properties | Y | N |
| 521 | does not accept mail (see rfc1846) | Y | N |
| 522 | Recipient has exceeded mailbox limit | Y | N |
| 523 | The total size of your mailing exceeds the recipient server’s limits | Y | N |
| 530 | Access denied: may be authentication, blacklist, or invalid email address | Y | N |
| 531 | Mail system Full | Y | N |
| 533 | Remote server has insufficient disk space to hold email | Y | N |
| 534 | Authentication mechanism is too weak. Message too big | Y | N |
| 535 | Multiple servers using same IP. Required Authentication | Y | N |
| 538 | Encryption required for requested authentication mechanism | Y | N |
| 541 | The recipient address rejected your message: normally, it’s an error caused by an anti-spam filter | Y | N |
| 542 | Bad Connection | Y | N |
| 543 | Routing server failure. No available route | Y | N |
| 546 | Email looping | Y | N |
| 547 | Delivery time-out | Y | N |
| 550 | Requested action not taken: mailbox unavailable | Y | N |
| 551 | User not local; please try | N | Y |
| 552 | Requested mail action aborted: exceeded storage allocation | Y | N |
| 553 | Requested action not taken: mailbox name not allowed | N | Y |
| 554 | Transaction failed | Y | N |
| 557 | You are not allowed to send mail | Y | N |
| 571 | Delivery not authorized, message refused | Y | N |
| 590 | Unexpected response from SMTP server | Y | N |
| 591 | No response from SMTP server | Y | N |
| 592 | Failed to send command | Y | N |
ECM SMTP Enhanced Status Codes
| Enhanced Status Code | Description | Increase Bounce Count | Mark as Bad | Short Name |
|---|---|---|---|---|
| 2.0.0 | Other undefined status is the only undefined error code. It should be used for all errors for which only the class of the error is known. | N | N | Successfully Sent – Other undefined Status |
| 2.1.5 | This mailbox address as specified was valid. This status code should be used for positive delivery reports. | N | N | Successfully Sent – Destination address valid |
| 2.6.4 | 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. This may also be a permanent error if the sender has indicated that conversion with loss is prohibited for the message. | N | N | Successfully Sent – Conversion with loss performed |
| 2.7.7 | A transport system otherwise authorized to validate a message was unable to do so because the message was corrupted or altered. This may be useful as a permanent, transient persistent, or successful delivery code. | N | N | Successfully Sent – Message integrity failure |
| 4.0.0 | Other undefined status is the only undefined error code. It should be used for all errors for which only the class of the error is known. | Y | N | Temporary problem – Other undefined Status |
| 4.1.0 | Something about the address specified in the message caused this DSN. | Y | N | Temporary problem – Other address status |
| 4.1.10 | This status code is returned when the associated address is marked as invalid using a null MX. | Y | N | Temporary problem – Recipient address has null MX |
| 4.1.4 | 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. | Y | N | Temporary problem – Destination mailbox address ambiguous |
| 4.1.7 | The sender’s address was syntactically invalid. This can apply to any field in the address. | Y | N | Temporary problem – Bad sender’s mailbox address syntax |
| 4.1.8 | The sender’s system specified in the address does not exist or is incapable of accepting return mail. For domain names, this means the address portion to the right of the “@” is invalid for mail. | N | N | Temporary problem – Bad sender’s system address |
| 4.1.9 | The mailbox address specified was valid, but the message has been relayed to a system that does not speak this protocol; no further information can be provided. | Y | N | Temporary problem – Message relayed to non-compliant mailer |
| 4.2.0 | The mailbox exists, but something about the destination mailbox has caused the sending of this DSN. | Y | N | Temporary problem – Other or undefined mailbox status |
| 4.2.1 | 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. | Y | N | Temporary problem – Mailbox disabled, not accepting messages |
| 4.2.2 | The mailbox is full because the user has exceeded a per-mailbox administrative quota or physical capacity. The general semantics implies that the recipient can delete messages to make more space available. This code should be used as a persistent transient failure. | Y | N | Temporary problem – Mailbox full |
| 4.2.4 | The mailbox is a mailing list address and the mailing list was unable to be expanded. This code may represent a permanent failure or a persistent transient failure. | Y | N | Temporary problem – Mailing list expansion problem |
| 4.3.0 | The destination system exists and normally accepts mail, but something about the system has caused the generation of this DSN. | Y | N | Temporary problem – Other or undefined mail system status |
| 4.3.1 | The recipient’s mailbox has exceeded itMail system storage has been exceeded. The general semantics imply that the individual recipient may not be able to delete material to make room for additional messages. This is useful only as a persistent transient error. | Y | N | Temporary problem – Mail system full |
| 4.3.2 | The host on which the mailbox is resident is not accepting messages. Examples of such conditions include an imminent shutdown, excessive load, or system maintenance. This is useful for both permanent and persistent transient errors. | Y | N | Temporary problem – System not accepting network messages |
| 4.3.3 | Selected features specified for the message are not supported by the destination system. This can occur in gateways when features from one domain cannot be mapped onto the supported feature in another. | Y | N | Temporary problem – System not capable of selected features |
| 4.3.5 | The system is not configured in a manner that will permit it to accept this message. | Y | N | Temporary problem – System incorrectly configured |
| 4.3.6 | The message was accepted for relay/delivery, but the requested priority (possibly the implied default) was not honoured. The human readable text after the status code contains the new priority, followed by SP (space) and explanatory human readable text. | Y | N | Temporary problem – Requested priority was changed |
| 4.4.0 | 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. | Y | N | Temporary problem – Other or undefined network or routing status |
| 4.4.1 | The outbound connection attempt was not answered, because either the remote system was busy, or was unable to take a call. This is useful only as a persistent transient error. | Y | N | Temporary problem – No answer from host |
| 4.4.2 | The outbound connection was established, but was unable to complete the message transaction, either because of time-out, or inadequate connection quality. This is useful only as a persistent transient error. | Y | N | Temporary problem – Bad connection |
| 4.4.3 | The network system was unable to forward the message, because a directory server was unavailable. This is useful only as a persistent transient error. The inability to connect to an Internet DNS server is one example of the directory server failure error. | Y | N | Temporary problem – Directory server failure |
| 4.4.4 | The mail system was unable to determine the next hop for the message because the necessary routing information was unavailable from the directory server. This is useful for both permanent and persistent transient errors. A DNS lookup returning only an SOA (Start of Administration) record for a domain name is one example of the unable to route error. | Y | N | Temporary problem – Unable to route |
| 4.4.5 | The mail system was unable to deliver the message because the mail system was congested. This is useful only as a persistent transient error. | Y | N | Temporary problem – Mail system congestion |
| 4.4.6 | A routing loop caused the message to be forwarded too many times, either because of incorrect routing tables or a user-forwarding loop. This is useful only as a persistent transient error. | Y | N | Temporary problem – Routing loop detected |
| 5.1.8 | The sender’s system specified in the address does not exist or is incapable of accepting return mail. For domain names, this means the address portion to the right of the “@” is invalid for mail. | Y | N | Permanent Error – Bad sender’s system address |
| 5.1.9 | The mailbox address specified was valid, but the message has been relayed to a system that does not speak this protocol; no further information can be provided. | Y | N | Permanent Error – Message relayed to non-compliant mailer |
| 5.2.0 | The mailbox exists, but something about the destination mailbox has caused the sending of this DSN. | Y | N | Permanent Error – Other or undefined mailbox status |
| 5.2.1 | 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. | Y | N | Permanent Error – Mailbox disabled, not accepting messages |
| 5.2.2 | The mailbox is full because the user has exceeded a per-mailbox administrative quota or physical capacity. The general semantics implies that the recipient can delete messages to make more space available. This code should be used as a persistent transient failure. | Y | N | Permanent Error – Mailbox full |
| 5.2.3 | A per-mailbox administrative message length limit has been exceeded. This status code should be used when the per-mailbox message length limit is less than the general system limit. This code should be used as a permanent failure. | Y | N | Permanent Error – Message length exceeds administrative limit |
| 5.2.4 | The mailbox is a mailing list address and the mailing list was unable to be expanded. This code may represent a permanent failure or a persistent transient failure. | Y | N | Permanent Error – Mailing list expansion problem |
| 5.3.0 | The destination system exists and normally accepts mail, but something about the system has caused the generation of this DSN. | Y | N | Permanent Error – Other or undefined mail system status |
| 5.3.2 | The host on which the mailbox is resident is not accepting messages. Examples of such conditions include an imminent shutdown, excessive load, or system maintenance. This is useful for both permanent and persistent transient errors. | Y | N | Permanent Error – System not accepting network messages |
| 5.3.3 | Selected features specified for the message are not supported by the destination system. This can occur in gateways when features from one domain cannot be mapped onto the supported feature in another. | Y | N | Permanent Error – System not capable of selected features |
| 5.3.4 | The message is larger than per-message size limit. This limit may either be for physical or administrative reasons. This is useful only as a permanent error. | Y | N | Permanent Error – Message too big for system |
| 5.3.5 | The system is not configured in a manner that will permit it to accept this message. | Y | N | Permanent Error – System incorrectly configured |
| 5.3.6 | The message was accepted for relay/delivery, but the requested priority (possibly the implied default) was not honoured. The human readable text after the status code contains the new priority, followed by SP (space) and explanatory human readable text. | Y | N | Permanent Error – Requested priority was changed |
| 5.4.0 | 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. | Y | N | Permanent Error – Other or undefined network or routing status |
| 5.4.4 | The mail system was unable to determine the next hop for the message because the necessary routing information was unavailable from the directory server. This is useful for both permanent and persistent transient errors. A DNS lookup returning only an SOA (Start of Administration) record for a domain name is one example of the unable to route error. | Y | N | Permanent Error – Unable to route |
| 5.4.7 | 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. If possible, the code for the actual problem found when delivery was attempted should be returned rather than this code. | Y | N | Permanent Error – Delivery time expired |
| 5.5.0 | 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. | Y | N | Permanent Error – Other or undefined protocol status |
| 5.5.1 | A mail transaction protocol command was issued which was either out of sequence or unsupported. This is useful only as a permanent error. | Y | N | Permanent Error – Invalid command |
| 5.5.2 | A mail transaction protocol command was issued which could not be interpreted, either because the syntax was wrong or the command is unrecognized. This is useful only as a permanent error. | Y | N | Permanent Error – Syntax error |
| 5.5.3 | More recipients were specified for the message than could have been delivered by the protocol. This error should normally result in the segmentation of the message into two, the remainder of the recipients to be delivered on a subsequent delivery attempt. It is included in this list in the event that such segmentation is not possible. | Y | N | Permanent Error – Too many recipients |
| 5.5.4 | A valid mail transaction protocol command was issued with invalid arguments, either because the arguments were out of range or represented unrecognized features. This is useful only as a permanent error. | Y | N | Permanent Error – Invalid command arguments |
| 5.5.5 | A protocol version mis-match existed which could not be automatically resolved by the communicating parties. | Y | N | Permanent Error – Wrong protocol version |
| 5.5.6 | This enhanced status code SHOULD be returned when the server fails the AUTH command due to the client sending a [BASE64] response which is longer than the maximum buffer size available for the currently selected SASL mechanism. This is useful for both permanent and persistent transient errors. | Y | N | Permanent Error – Authentication Exchange line is too long |
| 5.6.0 | 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. | Y | N | Permanent Error – Other or undefined media error |
| 5.6.1 | The media of the message is not supported by either the delivery protocol or the next system in the forwarding path. This is useful only as a permanent error. | Y | N | Permanent Error – Media not supported |
| 5.6.2 | The content of the message must be converted before it can be delivered and such conversion is not permitted. Such prohibitions may be the expression of the sender in the message itself or the policy of the sending host. | Y | N | Permanent Error – Conversion required and prohibited |
| 5.6.3 | The message content must be converted in order to be forwarded but such conversion is not possible or is not practical by a host in the forwarding path. This condition may result when an ESMTP gateway supports 8bit transport but is not able to downgrade the message to 7 bit as required for the next hop. | Y | N | Permanent Error – Conversion required but not supported |
| 5.6.4 | 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. This may also be a permanent error if the sender has indicated that conversion with loss is prohibited for the message. | Y | N | Permanent Error – Conversion with loss performed |
| 5.6.5 | A conversion was required but was unsuccessful. This may be useful as a permanent or persistent temporary notification. | Y | N | Permanent Error – Conversion Failed |
| 5.6.6 | The message content could not be fetched from a remote system. This may be useful as a permanent or persistent temporary notification. | Y | N | Permanent Error – Message content not available |
| 5.6.7 | This indicates the reception of a MAIL or RCPT command that non-ASCII addresses are not permitted | Y | N | Permanent Error – Non-ASCII addresses not permitted for that sender/recipient |
| 5.6.8 | This indicates that a reply containing a UTF-8 string is required to show the mailbox name, but that form of response is not permitted by the SMTP client. | Y | N | Permanent Error – UTF-8 string reply is required, but not permitted by the SMTP client |
| 5.6.9 | This indicates that transaction failed after the final “.” of the DATA command. | Y | N | Permanent Error – UTF-8 header message cannot be transferred to one or more recipients, so the message must be rejected |
| 5.7.0 | 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. This status code may also be used when the condition cannot be further described because of security policies in force. | Y | N | Permanent Error – Other or undefined security status |
| 5.7.1 | The sender is not authorized to send to the destination. This can be the result of per-host or per-recipient filtering. This memo does not discuss the merits of any such filtering, but provides a mechanism to report such. This is useful only as a permanent error. | Y | N | Permanent Error – Delivery not authorized, message refused |
| 5.7.10 | This indicates that external strong privacy layer is needed in order to use the requested authentication mechanism. This is primarily intended for use with clear text authentication mechanisms. A client which receives this may activate a security layer such as TLS prior to authenticating, or attempt to use a stronger mechanism. | Y | N | Permanent Error – Encryption Needed |
| 5.7.11 | This response to the AUTH command indicates that the selected authentication mechanism may only be used when the underlying SMTP connection is encrypted. Note that this response code is documented here for historical purposes only. Modern implementations SHOULD NOT advertise mechanisms that are not permitted due to lack of encryption, unless an encryption layer of sufficient strength is currently being employed. | Y | N | Permanent Error – Encryption required for requested authentication mechanism |
| 5.7.12 | This response to the AUTH command indicates that the user needs to transition to the selected authentication mechanism. This is typically done by authenticating once using the [PLAIN] authentication mechanism. The selected mechanism SHOULD then work for authentications in subsequent sessions. | Y | N | Permanent Error – A password transition is needed |
| 5.7.13 | Sometimes a system administrator will have to disable a user’s account (e.g., due to lack of payment, abuse, evidence of a break-in attempt, etc). This error code occurs after a successful authentication to a disabled account. This informs the client that the failure is permanent until the user contacts their system administrator to get the account re-enabled. It differs from a generic authentication failure where the client’s best option is to present the passphrase entry dialog in case the user simply mistyped their passphrase. | Y | N | Permanent Error – User Account Disabled |
| 5.7.14 | The submission server requires a configured trust relationship with a third-party server in order to access the message content. This value replaces the prior use of X.7.8 for this error condition. thereby updating [RFC4468]. | Y | N | Permanent Error – Trust relationship required |
| 5.7.15 | The specified priority level is below the lowest priority acceptable for the receiving SMTP server. This condition might be temporary, for example the server is operating in a mode where only higher priority messages are accepted for transfer and delivery, while lower priority messages are rejected. | Y | N | Permanent Error – Priority Level is too low |
| 5.7.16 | The message is too big for the specified priority. This condition might be temporary, for example the server is operating in a mode where only higher priority messages below certain size are accepted for transfer and delivery. | Y | N | Permanent Error – Message is too big for the specified priority |
| 5.7.17 | This status code is returned when a message is received with a Require-Recipient-Valid-Since field or RRVS extension and the receiving system is able to determine that the intended recipient mailbox has not been under continuous ownership since the specified date-time. | Y | N | Permanent Error – Mailbox owner has changed |
| 5.7.18 | This status code is returned when a message is received with a Require-Recipient-Valid-Since field or RRVS extension and the receiving system wishes to disclose that the owner of the domain name of the recipient has changed since the specified date-time. | Y | N | Permanent Error – Domain owner has changed |
| 5.7.19 | This status code is returned when a message is received with a Require-Recipient-Valid-Since field or RRVS extension and the receiving system cannot complete the requested evaluation because the required timestamp was not recorded. The message originator needs to decide whether to reissue the message without RRVS protection. | Y | N | Permanent Error – RRVS test cannot be completed |
| 5.7.2 | The sender is not authorized to send a message to the intended mailing list. This is useful only as a permanent error. | N | Y | Permanent Error – Mailing list expansion prohibited |
| 4.4.7 | 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. If possible, the code for the actual problem found when delivery was attempted should be returned rather than this code. | Y | N | Temporary problem – Delivery time expired |
| 4.5.0 | 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. | Y | N | Temporary problem – Other or undefined protocol status |
| 4.5.3 | More recipients were specified for the message than could have been delivered by the protocol. This error should normally result in the segmentation of the message into two, the remainder of the recipients to be delivered on a subsequent delivery attempt. It is included in this list in the event that such segmentation is not possible. | Y | N | Temporary problem – Too many recipients |
| 4.5.5 | A protocol version mis-match existed which could not be automatically resolved by the communicating parties. | Y | N | Temporary problem – Wrong protocol version |
| 4.5.6 | This enhanced status code SHOULD be returned when the server fails the AUTH command due to the client sending a [BASE64] response which is longer than the maximum buffer size available for the currently selected SASL mechanism. This is useful for both permanent and persistent transient errors. | Y | N | Temporary problem – Authentication Exchange line is too long |
| 4.6.0 | 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. | Y | N | Temporary problem – Other or undefined media error |
| 4.6.2 | The content of the message must be converted before it can be delivered and such conversion is not permitted. Such prohibitions may be the expression of the sender in the message itself or the policy of the sending host. | Y | N | Temporary problem – Conversion required and prohibited |
| 4.6.3 | The message content must be converted in order to be forwarded but such conversion is not possible or is not practical by a host in the forwarding path. This condition may result when an ESMTP gateway supports 8bit transport but is not able to downgrade the message to 7 bit as required for the next hop. | Y | N | Temporary problem – Conversion required but not supported |
| 4.6.4 | 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. This may also be a permanent error if the sender has indicated that conversion with loss is prohibited for the message. | Y | N | Temporary problem – Conversion with loss performed |
| 4.6.5 | A conversion was required but was unsuccessful. This may be useful as a permanent or persistent temporary notification. | Y | N | Temporary problem – Conversion Failed |
| 4.6.6 | The message content could not be fetched from a remote system. This may be useful as a permanent or persistent temporary notification. | Y | N | Temporary problem – Message content not available |
| 4.6.7 | This indicates the reception of a MAIL or RCPT command that non-ASCII addresses are not permitted | Y | N | Temporary problem – Non-ASCII addresses not permitted for that sender/recipient |
| 4.6.8 | This indicates that a reply containing a UTF-8 string is required to show the mailbox name, but that form of response is not permitted by the SMTP client. | Y | N | Temporary problem – UTF-8 string reply is required, but not permitted by the SMTP client |
| 4.6.9 | This indicates that transaction failed after the final “.” of the DATA command. | Y | N | Temporary problem – UTF-8 header message cannot be transferred to one or more recipients, so the message must be rejected |
| 4.7.0 | 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. This status code may also be used when the condition cannot be further described because of security policies in force. | Y | N | Temporary problem – Other or undefined security status |
| 4.7.10 | This indicates that external strong privacy layer is needed in order to use the requested authentication mechanism. This is primarily intended for use with clear text authentication mechanisms. A client which receives this may activate a security layer such as TLS prior to authenticating, or attempt to use a stronger mechanism. | Y | N | Temporary problem – Encryption Needed |
| 4.7.11 | This response to the AUTH command indicates that the selected authentication mechanism may only be used when the underlying SMTP connection is encrypted. Note that this response code is documented here for historical purposes only. Modern implementations SHOULD NOT advertise mechanisms that are not permitted due to lack of encryption, unless an encryption layer of sufficient strength is currently being employed. | Y | N | Temporary problem – Encryption required for requested authentication mechanism |
| 4.7.12 | This response to the AUTH command indicates that the user needs to transition to the selected authentication mechanism. This is typically done by authenticating once using the [PLAIN] authentication mechanism. The selected mechanism SHOULD then work for authentications in subsequent sessions. | Y | N | Temporary problem – A password transition is needed |
| 4.7.13 | Sometimes a system administrator will have to disable a user’s account (e.g., due to lack of payment, abuse, evidence of a break-in attempt, etc). This error code occurs after a successful authentication to a disabled account. This informs the client that the failure is permanent until the user contacts their system administrator to get the account re-enabled. It differs from a generic authentication failure where the client’s best option is to present the passphrase entry dialog in case the user simply mistyped their passphrase. | Y | N | Temporary problem – User Account Disabled |
| 4.7.14 | The submission server requires a configured trust relationship with a third-party server in order to access the message content. This value replaces the prior use of X.7.8 for this error condition. thereby updating [RFC4468]. | Y | N | Temporary problem – Trust relationship required |
| 4.7.15 | The specified priority level is below the lowest priority acceptable for the receiving SMTP server. This condition might be temporary, for example the server is operating in a mode where only higher priority messages are accepted for transfer and delivery, while lower priority messages are rejected. | Y | N | Temporary problem – Priority Level is too low |
| 4.7.16 | The message is too big for the specified priority. This condition might be temporary, for example the server is operating in a mode where only higher priority messages below certain size are accepted for transfer and delivery. | Y | N | Temporary problem – Message is too big for the specified priority |
| 4.7.17 | This status code is returned when a message is received with a Require-Recipient-Valid-Since field or RRVS extension and the receiving system is able to determine that the intended recipient mailbox has not been under continuous ownership since the specified date-time. | Y | N | Temporary problem – Mailbox owner has changed |
| 4.7.18 | This status code is returned when a message is received with a Require-Recipient-Valid-Since field or RRVS extension and the receiving system wishes to disclose that the owner of the domain name of the recipient has changed since the specified date-time. | Y | N | Temporary problem – Domain owner has changed |
| 4.7.19 | This status code is returned when a message is received with a Require-Recipient-Valid-Since field or RRVS extension and the receiving system cannot complete the requested evaluation because the required timestamp was not recorded. The message originator needs to decide whether to reissue the message without RRVS protection. | Y | N | Temporary problem – RRVS test cannot be completed |
| 4.7.20 | This status code is returned when a message did not contain any passing DKIM signatures. (This violates the advice of Section 6.1 of [RFC6376].) | Y | N | Temporary problem – No passing DKIM signature found |
| 4.7.21 | This status code is returned when a message contains one or more passing DKIM signatures, but none are acceptable. (This violates the advice of Section 6.1 of [RFC6376].) | Y | N | Temporary problem – No acceptable DKIM signature found |
| 4.7.22 | This status code is returned when a message contains one or more passing DKIM signatures, but none are acceptable because none have an identifier(s) that matches the author address(es) found in the From header field. This is a special case of 7.21. (This violates the advice of Section 6.1 of [RFC6376].) | Y | N | Temporary problem – No valid author-matched DKIM signature found |
| 4.7.23 | This status code is returned when a message completed an SPF check that produced a “fail” result, contrary to local policy requirements. Used in place of 5.7.1 as described in Section 8.4 of [RFC7208]. | Y | N | Temporary problem – SPF validation failed |
| 4.7.24 | This status code is returned when evaluation of SPF relative to an arriving message resulted in an error. Used in place of 4.4.3 or 5.5.2 as described in Sections 8.6 and 8.7 of RFC7208. | Y | N | Temporary problem – SPF validation error |
| 4.7.25 | This status code is returned when an SMTP client’s IP address failed a reverse DNS validation check, contrary to local policy requirements. | Y | N | Temporary problem – Reverse DNS validation failed |
| 4.7.26 | This status code is returned when a message failed more than one message authentication check, contrary to local policy requirements. The particular mechanisms that failed are not specified. | Y | N | Temporary problem – Multiple authentication checks failed |
| 4.7.27 | This status code is returned when the associated sender address has a null MX, and the SMTP receiver is configured to reject mail from such sender (e.g., because it could not return a DSN). | Y | N | Temporary problem – Sender address has null MX |
| 4.7.28 | Mail flood detected | Y | N | Temporary problem – Mail flood detected |
| 4.7.5 | 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. | Y | N | Temporary problem – Cryptographic failure |
| 4.7.6 | A transport system otherwise authorized to validate or decrypt a message was unable to do so because the necessary algorithm was not supported. | Y | N | Temporary problem – Cryptographic algorithm not supported |
| 4.7.7 | A transport system otherwise authorized to validate a message was unable to do so because the message was corrupted or altered. This may be useful as a permanent, transient persistent, or successful delivery code. | Y | N | Temporary problem – Message integrity failure |
| 4.7.8 | This response to the AUTH command indicates that the authentication failed due to invalid or insufficient authentication credentials. In this case, the client SHOULD ask the user to supply new credentials (such as by presenting a password dialog box). | Y | N | Temporary problem – Authentication credentials invalid |
| 4.7.9 | This response to the AUTH command indicates that the selected authentication mechanism is weaker than server policy permits for that user. The client SHOULD retry with a new authentication mechanism. | Y | N | Temporary problem – Authentication mechanism is too weak |
| 5.0.0 | Other undefined status is the only undefined error code. It should be used for all errors for which only the class of the error is known. | Y | N | Permanent Error – Other undefined Status |
| 5.1.0 | Something about the address specified in the message caused this DSN. | Y | N | Permanent Error – Other address status |
| 5.1.1 | The mailbox specified in the address does not exist. For Internet mail names, this means the address portion to the left of the “@” sign is invalid. This code is only useful for permanent failures. | N | Y | Permanent Error – Bad destination mailbox address |
| 5.1.10 | This status code is returned when the associated address is marked as invalid using a null MX. | Y | N | Permanent Error – Recipient address has null MX |
| 5.1.2 | The destination system specified in the address does not exist or is incapable of accepting mail. For Internet mail names, this means the address portion to the right of the “@” is invalid for mail. This code is only useful for permanent failures. | N | Y | Permanent Error – Bad destination system address |
| 5.1.3 | The destination address was syntactically invalid. This can apply to any field in the address. This code is only useful for permanent failures. | N | Y | Permanent Error – Bad destination mailbox address syntax |
| 5.1.4 | 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. | Y | N | Permanent Error – Destination mailbox address ambiguous |
| 5.1.6 | The mailbox address provided was at one time valid, but mail is no longer being accepted for that address. This code is only useful for permanent failures. | N | Y | Permanent Error – Destination mailbox has moved, No forwarding address |
| 5.1.7 | The sender’s address was syntactically invalid. This can apply to any field in the address. | Y | N | Permanent Error – Bad sender’s mailbox address syntax |
| 5.7.20 | This status code is returned when a message did not contain any passing DKIM signatures. (This violates the advice of Section 6.1 of [RFC6376].) | Y | N | Permanent Error – No passing DKIM signature found |
| 5.7.21 | This status code is returned when a message contains one or more passing DKIM signatures, but none are acceptable. (This violates the advice of Section 6.1 of [RFC6376].) | Y | N | Permanent Error – No acceptable DKIM signature found |
| 5.7.22 | This status code is returned when a message contains one or more passing DKIM signatures, but none are acceptable because none have an identifier(s) that matches the author address(es) found in the From header field. This is a special case of X.7.21. (This violates the advice of Section 6.1 of [RFC6376].) | Y | N | Permanent Error – No valid author-matched DKIM signature found |
| 5.7.23 | This status code is returned when a message completed an SPF check that produced a “fail” result, contrary to local policy requirements. Used in place of 5.7.1 as described in Section 8.4 of [RFC7208]. | Y | N | Permanent Error – SPF validation failed |
| 5.7.24 | This status code is returned when evaluation of SPF relative to an arriving message resulted in an error. Used in place of 4.4.3 or 5.5.2 as described in Sections 8.6 and 8.7 of RFC7208. | Y | N | Permanent Error – SPF validation error |
| 5.7.25 | This status code is returned when an SMTP client’s IP address failed a reverse DNS validation check, contrary to local policy requirements | Y | N | Permanent Error – Reverse DNS validation failed |
| 5.7.26 | This status code is returned when a message failed more than one message authentication check, contrary to local policy requirements. The particular mechanisms that failed are not specified. | Y | N | Permanent Error – Multiple authentication checks failed |
| 5.7.27 | This status code is returned when the associated sender address has a null MX, and the SMTP receiver is configured to reject mail from such sender (e.g., because it could not return a DSN). | Y | N | Permanent Error – Sender address has null MX |
| 5.7.28 | The message appears to be part of a mail flood of similar abusive message. | Y | N | Permanent Error – Mail flood detected |
| 5.7.3 | A conversion from one secure messaging protocol to another was required for delivery and such conversion was not possible. This is useful only as a permanent error. | Y | N | Permanent Error – Security conversion required but not possible |
| 5.7.4 | A message contained security features such as secure authentication that could not be supported on the delivery protocol. This is useful only as a permanent error. | Y | N | Permanent Error – Security features not supported |
| 5.7.5 | 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. | Y | N | Permanent Error – Cryptographic failure |
| 5.7.6 | A transport system otherwise authorized to validate or decrypt a message was unable to do so because the necessary algorithm was not supported. | Y | N | Permanent Error – Cryptographic algorithm not supported |
| 5.7.64 | Office 365 or multiple registered domains | Y | N | Permanent Error – TenantAttribution; Relay Access Denied |
| 5.7.66 | Requested action not taken: mailbox unavailable | N | N | Permanent Error – mailbox unavailable |
| 5.7.7 | A transport system otherwise authorized to validate a message was unable to do so because the message was corrupted or altered. This may be useful as a permanent, transient persistent, or successful delivery code. | Y | N | Permanent Error – Message integrity failure |
| 5.7.8 | This response to the AUTH command indicates that the authentication failed due to invalid or insufficient authentication credentials. In this case, the client SHOULD ask the user to supply new credentials (such as by presenting a password dialog box). | Y | N | Permanent Error – Authentication credentials invalid |
| 5.7.9 | This response to the AUTH command indicates that the selected authentication mechanism is weaker than server policy permits for that user. The client SHOULD retry with a new authentication mechanism. | Y | N | Permanent Error – Authentication mechanism is too weak |
| 5.9.8 | Spam | N | N | Permanent Error – Spam |
Once an email address on a customer record is marked as BAD, the email address is not displayed on the SSA (self service administration) to the customer. Only in the back-office on the customer record would the email address continue to be displayed.
When an email message is bounced back from the recipient’s email server, the SMTP response is displayed in the E-Contact switchview on the customer record, under the Message Summary sub-tab.
The “Increase Bounce Count” and “Mark as Bad” values in ECM SMTP Response Reply Codes and ECM SMTP Enhanced Status Codes have been set by ACGI.
Increased Bounce Count: If the email message sent from ACGI, was returned as undeliverable, then the system increases the “Bounce Count” tied to the customer’s email address that was used.
Mark as Bad: If the email message sent from ACGI, was returned as undeliverable, then the system updates the “Bad Address Date” tied to the customer’s email address, with the day the response was received.
Ensure the system parameter ECM_MAX_BOUNCES is set to the number of bounces (bounce count) that you wish for the system to reference to determine when to mark a customer’s email address as BAD. The default value for this parameter is set to 5. This means that once a customer’s email address receives their 5th bounce, the system will automatically set the email address to BAD and the email address will no longer be used when sending messages from the system.