Client and segregation codes
Codes starting with 100 are related to client segregation and indicates that a valid client cannot be determined by the MTA.
Code | Message | Type | Rejection reason |
|---|---|---|---|
ETP100 | Invalid recipient | Reject | Invalid domain specified. The specified domain doesn't match a known inline or OOB domain. |
ETP101 | Invalid recipient | Reject | Invalid BCC recipient specified. The domain matched a valid BCC domain however the recipient did not match a known client BCC recipient. |
ETP102 | Invalid recipient | Reject | Invalid recipient specified. The upstream MTA rejected the recipient and mail cannot be delivered to this recipient. |
ETP103 | Invalid recipient | Defer | Unable to validate recipient via SMTP. The upstream MTA did not respond in time to validate the recipient and the recipient is not cached as a known recipient. |
ETP104 | Routing loop detected | Reject | Routing loop detected. We have detected a routing loop with the sending MTA and have rejected the email. |
ETP105 | Invalid domain mode | Reject | Invalid recipient domain mode. The specified domain has an invalid mode. |
ETP106 | Requested action aborted | Defer | Requested action aborted: Try again later. MTA-MTA_API communication failed and we were unable to validate the recipient and have rejected the recipient. |
ETP107 | Invalid recipient | Reject Rcpt | Invalid recipient specified. The current recipient does not belong to the same domain as the earlier recipient specified. Email Security — Cloud is configured to accept messages to multiple recipients, only if they all belong to the same domain. |
ETP108 | Invalid sender | Reject | Invalid sender specified. This check happens specifically when a customer is reporting an FP/FN. In this case, the MTA has detected that the sender does not belong to any configured domain (is not our customer). |
ETP109 | Requested action aborted: try again later | Defer | No Message Analyses Policy associated to Domain. |
ETP110 | Organization is receiving message exceeding the limits | Defer | Bandwidth usage is over the pre-defined limit. |
ETP111 | Domain token key header missing | Defer | Domain Identification key is missing in message header. For outbound scanning, you must create a Domain Identification key and include it in the header of the email you want to send using the following format: X-ETP-DOMAIN-AUTH-TOKEN: <identification-key> |
ETP112 | Organization is sending message exceeding the limit | Defer | Bandwidth usage is over the pre-defined limit. |
ETP114 | Sender is sending message exceeding the configured rate limit | Defer | Message usage is over the configured rate limit. |
Spam and attack codes
Codes starting with 200 are related to spam and attack protection services and indicates that the sending MTA is untrusted.
Code | Message | Type | Rejection reason |
|---|---|---|---|
ETP200 | Invalid recipient | Reject | Directory Harvest Attack Protection. Too many failed recipient checks causes Directory Harvest Attack Protection to kick in and ban a sending MTA. |
ETP202 | Your IP ($(_ipsrc)) is listed by Spamhaus. Please see http://www.spamhaus.org/query/ip/$(_ipsrc) if you feel this is in error. | Reject | Spamhaus Zen RBL Protection. The sending MTA IP address was listed on the Spamhaus Zen RBL. |
ETP203 | SPF Failure for domain (<domain>). | Reject | SPF failure for sending domain. |
ETP204 | DKIM Failure for domain (<domain>). | Reject | DKIM failure for sending domain. |
ETP205 | DMARC Failure for domain (<domain>). | Reject | DMARC failure for sending domain. |
ETP206 | Unknown sender reputation | Defer | Unknown sender profile, temporarily deferring incoming injection. |
ETP207 | Your IP %s is listed by Invaluement. Please see http://www.invaluement.com/research/ if you feel this is in error. | Reject | The sending MTA IP address was listed on Invaluement Sip RBL. |
ETP208 | Your IP %s is listed by Invaluement. Please see http://www.invaluement.com/research/ if you feel this is in error. | Reject | The sending MTA IP address was listed on Invaluement Sip24 RBL. |
ETP210 | ETP210 = Your DNS %s is listed by Spamhaus. Please see http://www.spamhaus.org/query/domain/ if you feel this is in error. | Reject | The sending domain was listed on Spamhaus Dbl RBL. |
ETP211 | Your DNS %s is listed by Invaluement. Please see http://www.invaluement.com/research/ if you feel this is in error. | Reject | The sending domain was listed on Invaluement Uri RBL. |
ETP212 | Your DNS %s is listed by Newexist. | Reject | The sending domain was listed on Newexist RBL. |
ETP220 | Your IP is listed by Spamcop and two other RBLs | Reject | The sending IP is listed by Spamcop and two other RBLs |
ETP221 | Your IP is listed by Barracuda and two other RBLs | Reject | The sending IP is listed by Barracuda and two other RBLs |
ETP222 | Your IP is listed by Spameatingmonkey and two other RBLs | Reject | The sending IP is listed by Spameatingmonkey and two other RBLs |
ETP223 | Your IP is listed by Manitu and two other RBLs | Reject | The sending IP is listed by Manitu and two other RBLs |
ETP224 | Your IP is listed by Uceprotect and two other RBLs | Reject | The sending IP is listed by Uceprotect and two other RBLs |
ETP225 | Your IP is listed by Surriel and two other RBLs | Reject | The sending IP is listed by Surriel and two other RBLs |
ETP226 | Your IP is listed by Junkemailfilter and two other RBLs | Reject | The sending IP is listed by Junkemailfilter and two other RBLs |
ETP227 | Your IP is listed by Justspam and two other RBLs | Reject | The sending IP is listed by Justspam and two other RBLs |
ETP230 | Your IP %s is listed on too many RBLs. | Reject | The sending MTA IP address was listed on too many RBLs. |
Client configuration codes
Codes starting with 300 are related to configuration issues for a client domain. The client is responsible for fixing these types of errors.
Code | Message | Type | Rejection reason |
|---|---|---|---|
ETP300 | StartTLS required for this domain | Reject | StartTLS was not issued for the SMTP transaction and the domain requires TLS to receive email. |
ETP301 | Invalid IP/sender domain | Reject | Invalid IP address for the sending MTA. The sending MTA's IP address does not match the IP address specified in the incoming MTA's table. |
ETP302 | Email size exceeds limit | Reject | Email Size Limit Exceeded. The DATA size exceeded the client configured size limit or the global size limit of 35 MB. |
ETP303 | StartTLS required for this transaction. | Reject | This error may occur early in SMTP conversation, prior to client identification. As a result may not show up in Email Trace. |
Client denylist codes
Codes starting with 400 are related to configuration issues for a client domain. The client is responsible for fixing these types of errors.
Code | Message | Type | Rejection reason |
|---|---|---|---|
ETP400 | Invalid recipient | Reject | IP Address Denylist. The sending MTA IP address matched a denylist entry specified by the client. |
ETP401 | Invalid recipient | Reject | Reverse DNS Denylist. The sending MTA IP addresses reverse DNS entry matched a denylist entry specified by the client. |
ETP402 | Invalid recipient | Reject | Country Denylist. The sending MTA IP address country matched a denylist entry specified by the client. |
ETP403 | Invalid recipient | Reject | Recipient Denylist. The RCPT TO value matched a denylist entry specified by the client. |
ETP404 | Invalid recipient | Reject | Sender Denylist. The MAIL FROM value matched a denylist entry specified by the client. |
ETP405 | Invalid recipient | Reject | Sender Domain Denylist. The MAIL FROM domain value matched a denylist entry specified by the client. |