| Deferral |
All connection backlog slots used up for this domain. |
GreenArrow did not attempt remote delivery for this message due to throttling. This will appear in logs and delivery_attempt events as having status=connmaxout. This message is only produced when the legacy_behavior option single_connmaxout_message is enabled. |
| Deferral |
All connection backlog slots full due to max concurrent connections. |
GreenArrow did not attempt remote delivery for this message due to throttling. This will appear in logs and delivery_attempt events as having status=connmaxout. This message is not produced when the legacy_behavior option single_connmaxout_message is enabled. |
| Deferral |
All connection backlog slots full due to max delivery attempts per hour. |
GreenArrow did not attempt remote delivery for this message due to throttling. This will appear in logs and delivery_attempt events as having status=connmaxout. This message is not produced when the legacy_behavior option single_connmaxout_message is enabled. |
| Deferral |
Deliveries to this recipient domain from this RFC5321.MailFrom domain are paused. |
GreenArrow did not attempt remote delivery for this message because of a domain pause. This will appear in logs and delivery_attempt events as having status=connmaxout. |
| Deferral |
Deliveries to this recipient domain from this RFC5322.From domain are paused. |
GreenArrow did not attempt remote delivery for this message because of a domain pause. This will appear in logs and delivery_attempt events as having status=connmaxout. |
| Failure |
Sorry, I couldn’t find any host named {HOSTNAME}. (#5.1.2) |
There are no MX or A DNS records for the recipient domain name (or the hostname of the server defined in a Relay Server VirtualMTA being used). |
| Failure |
Sorry, the host named {HOSTNAME} does not have any MX records, and delivery without MX records prohibited by local policy. (#5.1.0) |
There are no MX records for the recipient domain name and bounce_recipients_with_no_mx has been configured. |
| Failure |
Sorry, I couldn’t find a mail exchanger or IP address. (#5.4.4) |
Permanent error doing a MX/A record DNS lookup for the recipient domain name (or the hostname of the server defined in a Relay Server VirtualMTA being used). |
| Deferral |
Sorry, I couldn’t find any host by that name. (#4.1.2) |
Temporary error doing a MX/A record DNS lookup for the recipient domain name (or the hostname of the server defined in a Relay Server VirtualMTA being used).
This response can also be caused by all MX records containing malformed domain names. |
| Failure |
Sorry. Although I’m listed as a best-preference MX or A for that host,/it isn’t in my control/locals file, so I don’t treat it as local. (#5.4.6) |
There are no IP addresses for mail exchangers that are not on the local machine (or on the ipme list). GreenArrow, unless specifically overridden by configuration, will not connect to any IP addresses on the local machine (or the ipme list) to deliver mail. This avoids creating mail loops. |
| Deferral |
Sorry, I wasn’t able to bind to the outgoing IP address. (#4.4.1) |
Unable to bind to the IP address specified in the VirtualMTA IP Address or Relay Server configuration for making outgoing connections from. This typically means that the IP address is not configured in the operating system of the server. |
| Deferral |
Sorry, I wasn’t able to establish an SMTP connection. (#4.4.1) |
Unable to open a TCP connection to the SMTP server for this domain name (or for the SMTP server specified for a Relay Server VirtualMTA). (GreenArrow internally caches a list of IP addresses that it repeatedly gets errors connecting to, so that it does not hammer sites that are down with repeated connection attempts. This error may be due to this cache entry instead of an actual TCP connection attempt. This cache is automatically cleared, so GreenArrow will detect when sites come back up.
The meaning of this error message is modified when using the proxy_server configuration directive. See the Proxy Protocol documentation for more information. |
| Deferral, failure, or acceptance |
Connected to {IP} but connection died. (#4.4.2) |
Opened connection to IP address, but the connection died in the process of sending the email. |
| Deferral, failure, or acceptance |
Connected to {IP} but connection died. Possible duplicate! (#4.4.2) |
Opened connection to IP address, but the connection died in the process of sending the email. The connection died at the point where GreenArrow had sent the complete email, but had not yet received a notification that the remote host accepted or rejected the email. Thus, the email may have been accepted by the remote host and GreenArrow does not know about it, thus creating a duplicate message. |
| Deferral or failure |
Connected to {IP} but greeting failed/Remote host said: {MESSAGE} |
A greeting other than a 220 code was received when opening the SMTP connection. |
| Deferral |
Connected to {IP} but my name was rejected/Remote host said: {MESSAGE} |
The response to the HELO command (were we provide our server name to the remote host) was not a 250 code. |
| Deferral or failure |
Connected to {IP} but sender was rejected./Remote host said: {MESSAGE} |
The MAIL FROM command was rejected by remote host. |
| Deferral or failure |
{IP} does not like recipient./Remote host said: {MESSAGE}/Giving up on {IP} |
The RCPT TO command was rejected by remote host. |
| Deferral or failure |
{IP} failed on DATA command./Remote host said: {MESSAGE} |
The DATA command was rejected by remote host. |
| Failure |
SMTP cannot transfer messages with partial final lines. (#5.6.2) |
The SMTP RFC does not allow transmitting a message that does not end in a newline. This message does not end in a newline, therefor it can’t be transmitted without modification, thus the delivery attempt fails. |
| Deferral or failure |
{IP} failed after I sent message./Remote host said: {MESSAGE} |
Failure code received from remote host after sending message body. |
| Deferral, failure, or acceptance |
Connected to {IP} but connection died due to a TLS error. (#4.4.2) |
Opened connection to IP address, but the connection died in the process of sending the email due to a TLS error. |
| Deferral, failure, or acceptance |
Connected to {IP} but connection died due to a TLS error. Possible duplicate! (#4.4.2) |
Opened connection to IP address, but the connection died in the process of sending the email due to a TLS error. The connection died at the point where GreenArrow had sent the complete email, but had not yet received a notification that the remote host accepted or rejected the email. Thus, the email may have been accepted by the remote host and GreenArrow does not know about it, thus creating a duplicate message. |
| Deferral |
Connected to {IP} but the connection died while negotiating STARTTLS TLS. (#4.4.2) |
Opened connection to IP address, but the connection died while in the process of starting the TLS connection. |
| Deferral |
Connected to {IP} but STARTTLS TLS negotiation failed. (#4.4.2) |
The connection was established but an error was encountered after sending the STARTTLS command to the remote server. |
| Deferral |
Connected to {IP} but SMTPS TLS negotiation failed. (#4.4.1) |
The connection was established but an error was encountered while starting SMTPS TLS. |
| Deferral |
Sorry, the specified outgoing IP is not an IPv4 address. (#4.3.0) |
The connection could not be opened as the requested outgoing IP was not an IPv4 address |
| Deferral |
Connected to {IP} but the TLS negotiation failed. (#4.4.2) |
The connection was established but TLS negotiation failed to successfully complete. |
| Deferral |
Connected to {IP} but the connection died while negotiating TLS. (#4.4.2) |
The connection died while TLS negotiation was underway. |
| Deferral |
Connected to {IP} but SMTPS negotiation failed. (#4.4.1) |
The connection was established but SMTPS negotiation failed to successfully complete. |
| Deferral, failure, or acceptance |
Connected to {IP} but STARTTLS is not available, delivery attempt not made. (#5.7.10) |
The connection was successfully opened to the remote server, but STARTTLS is required and it was not available. |
| Deferral |
Sorry, the specified Relay Server IP is not an IPv4 address nor a domain name. (#4.3.0) |
The connection could not be opened because the specified Relay Server IP is neither an IPv4 address nor a domain name. |
| Deferral |
Sorry, the specified Relay Server IP is a domain name with no IPs found. (#4.3.0) |
The connection could not be opened because the specified Relay Server IP is a domain name with no IPv4 addresses. |
| Deferral |
Sorry, the specified destination port is not a valid port number. (#4.3.0) |
The connection could not be opened because the specified destination port is not a valid port number. |
| Failure |
Sorry, address must include host name. (#5.1.3) |
The connection could not be opened because the recipient email address does not include a host name. |
| Deferral |
Connection to proxy server cannot be established. (#4.4.1) |
None of the proxy_server servers configured for the outgoing IP could not be reached. A connection to the actual destination was not attempted. |
| Deferral |
Unable to connect to GreenArrow proxy for remote throttling. (#4.4.1) |
None of the greenarrow_proxy servers configured for the outgoing IP could not be reached. A connection to the actual destination was not attempted. This will appear in logs and delivery_attempt events as having status=connmaxout. |
| Deferral |
Connection to GreenArrow proxy server cannot be established. (#4.4.1) |
None of the greenarrow_proxy servers configured for the outgoing IP could not be reached. A connection to the actual destination was not attempted. This will appear in logs and delivery_attempt events as having status=connmaxout. |
| Deferral |
Sorry, an error was encountered while communicating with the GreenArrow proxy. (#XXX.4.1) |
There was a communication failure with the greenarrow_proxy server configured for the outgoing IP. This will appear in logs and delivery_attempt events as having status=connmaxout. |
