GreenArrow Email Software Documentation

Remote Delivery Attempt Error Messages

These are the error messages that can be created from a SMTP delivery attempt. These will appear in the SMTP log and reporting.

Basic Delivery Errors

Type of error Error message Description
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, 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).
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.
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.
Type of error Error message Description
Deferral Connected to {IP} but no authentication method was offered that I support/Remote host said: {MESSAGE} SMTP-AUTH is configured for this connection, and the server does not advertise either the PLAIN or LOGIN email authentication method.
Deferral Connected to {IP} but authentication was rejected (AUTH PLAIN)./Remote host said: {MESSAGE} SMTP-AUTH is configured for this connection, and AUTH PLAIN was advertised by the remote server, but an attempt to do AUTH PLAIN was rejected.
Deferral Connected to {IP} but authentication was rejected (plain)./Remote host said: {MESSAGE} SMTP-AUTH is configured for this connection, and the username and password was rejected as part of AUTH LOGIN attempt.
Deferral Connected to {IP} but authentication was rejected (AUTH LOGIN)./Remote host said: {MESSAGE} SMTP-AUTH is configured for this connection, AUTH LOGIN was advertised by the remote server, but an attempt to do AUTH LOGIN was rejected.
Deferral Connected to {IP} but authentication was rejected (username)./Remote host said: {MESSAGE} SMTP-AUTH is configured for this connection, and the username was rejected as part of AUTH LOGIN attempt.
Deferral Connected to {IP} but authentication was rejected (password)/Remote host said: {MESSAGE} SMTP-AUTH is configured for this connection, and the password was rejected as part of AUTH LOGIN attempt. (This error can still be due to an incorrect username, as many SMTP servers do not evaluate the username until receiving both the username and password.)

Delivery Override Errors

Deferral or failure Delivery attempt prevented by local configuration. (#5.7.1) The connection was not attempted due to a delivery override.
Acceptance This message was discarded by local configuration. (#2.7.1) The connection was not attempted due to a delivery override.

Internal Errors

Type of error Error message Description
Deferral Unable to read message. (#4.3.0) GreenArrow not able to read message from queue. Could be queue or filesystem corruption or operating system errors.
Deferral Internal error: found EOF early on multiqueue message. (#4.3.0) Internal error on format of queue files. Check for queue or filesystem corruption.
Deferral Internal error: invalid format on multiqueue header. (#4.3.0) Internal error on format of queue files. Check for queue or filesystem corruption.
Deferral Internal error: unable to seek to multiqueue message. (#4.3.0) Internal error on format of queue files. Check for queue or filesystem corruption.
Deferral Internal error: unable to parse pos from environment variable. (#4.3.0) Internal error on format of queue files. Check for queue or filesystem corruption.
Deferral Test temporary failure. Test failure message.
Deferral Internal error: System is shutting down This was a delivery attempt that was scheduled by one part of GreenArrow while a request to shutdown GreenArrow was received. In order to shut down as fast as possible, another part of GreenArrow created this deferral to clear the queue of scheduled delivery attempts.
Failure Test failure. Test failure message.
Deferral Internal error: helo host cannot be blank (#4.3.0) The connection could not be opened because the specified HELO host is blank.

Copyright © 2012–2019 GreenArrow Email