Explanation of socket response and error codes used in MailEnable log files


Various error codes that can be returned and displayed in the MailEnable log files.


MailEnable logs socket errors in the SMTP Debug Log file. Socket errors occur because the TCP/IP session between two computers was either interrupted or was closed by either party. The following sections label socket return codes and outline possible causes.

10053 : (WSAECONNABORTED) - Software caused connection abort.
(recv) socket [424] timeout during [] command from host Socket was disconnected - Return Value: (10053)

Software caused connection abort. An established connection was aborted by the software in the host computer, possibly due to a data transmission time-out or protocol error. This means that there was a communications failure while data was being sent or received from/by MailEnable. MailEnable was either expecting to receive a response from a remote server, but did not receive the response in an acceptable timeframe.

Probable Cause:
The most likely causes of this issue are:

  • Faulty network card
  • Bad or incompatible network card drivers
  • Unstable network connectivity (e.g. faulty router or bad carrier)
  • Firewall intervention - a local or external firewall prevented the transmission or receipt of data
  • Invalid MTU settings on network card, please see: https://www.mailenable.com/kb/content/article.asp?ID=ME020063

    10054 : (WSAECONNRESET) - Connection reset by peer.
    (recv) socket [424] timeout during [] command from host Socket was disconnected - Return Value: (10054)

    An existing connection was forcibly closed by the remote mail server or mail client application. This normally results if the remote mail server/mail client application is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close. This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress.

    Probable Cause:
    The most likely causes of this issue are:

  • Ungraceful rejection by remote mail host or mail client application. The remote mail server or mail client terminated its session with MailEnable without negotiating the appropriate closing sequence. The most likely reason for this is that you are blacklisted because your server is (or was) open relay. This can be confirmed by using the Blacklists lookup feature at MXToolbox . Confirm if the server is open relay by using the MailEnable Remote Diagnostic Utility.
  • Faulty network card/network card drivers
  • Remote host failed, or was rebooted/unstable remote host computer.
  • Port scan - someone has run a TCP/IP utility against the server to determine what services are running. Some ISPs may do this to determine what software is being used.

    10060 : (WSAECONNTIMEOUT) - Software caused connection abort.
    Socket was disconnected - Return Value: (10060)

    This error indicates that MailEnable dropped the connection because it did not receive data in a timely fashion.

    Probable Cause: The remote mail server is not sending the end of data command correctly. Some Unix mail servers and Perl mail scripts violate send "." to terminate the DATA command, but don't terminate the line correctly. So the mail server is waiting for more data, but it is never received and times out.


    Troubleshooting Mail Client Connectivity to MailEnable:Article ME020075

    Error 10038 when communicating with remote hosts:Article ME020238

    How to troubleshoot SMTP Connectivity issues and Analyse Log Files:Article ME020170

    Product:MailEnable (All Versions)
    Class:INF: Product Information
    Created:18/02/2003 12:41:00 PM
    Revised:Thursday, March 28, 2019