Logout

Alt-N Discussion Groups > MDaemon Discussion Groups > MDaemon Support > Archive > Socket error 10054 - Connection was reset by the other side!

 [F] Alt-N Discussion Groups  / MDaemon Discussion Groups  / MDaemon Support  / Archive  /

Socket error 10054 - Connection was reset by the other side!

[Ilie, Voinea]
Voinea Ilie
Newbie
Newbie
Posts: 14
Voinea Ilie - 06:25am, Jan 17 2022

We have a lot of sessions that are ending with the error Socket error 10054 - Connection was reset by the other side!
How can I identify what kind of problems are causing this error?

Mdaemon(64) 12.5.1
Thank you!

  All MessagesOldest ItemsOlder ItemsNewer ItemsNewest Items

Arron Caruth - Jan 17, 2022 8:19 am (#1 Total: 4)  

Guest User  

Photo of Author
Posts: 1
Can you confirm the version of MDaemon you are using?  There is not a 64 bit version of MDaemon 12.5.1, so I just want to confirm.

Technically MDaemon 12.5.1 is no supported, but I can try to provide some information to point you in the right direction. Winsock error 10054 means that the remote host forcibly closed the connection.  There are a lot of reasons this could be occurring.  If you have access to the logs on the server that is ending the session, it could provide helpful information.  

Does this occur with specific hosts or with all hosts?  If its only happening with specific hosts, I'd attempt to contact them to see if they can help figure out what it is happening.  Running a trace route to the hosts you are having issues with may provide some insight.

If its occurring with all hosts, I'd suggest checking your infrastructure to ensure everything is configured properly.  Check to make sure your internet connection is not going offline and then back online. If you reset your firewall, router, modem, proxy, and reboot the MDaemon machine, does the problem go away? Run a speed test using something like speedtest.net. Is your firewall dropping the connections? What do the firewall logs show?  Do you have a proxy, what do the proxy logs show? You may even need to check your ISP to make sure something isn't wrong there. 

Basically, this error could be caused by anything from your server to the receiving server and everything in between.  

You should also check the MDaemon logs to see if the error is occurring at the same location in the SMTP session each time.  Does it only happen with messages over a certain size.   

I hope that helps.
--
Arron Caruth
Vice President of Product Development
o: 817-601-3222    e: Arron.Caruth@mdaemon.com

MDaemon Technologies
Simple Secure Email

Visit us on www.mdaemon.com | Facebook | LinkedIn | YouTube
Sent using the MDaemon Email Server

On Mon, 17 Jan 2022 06:25:21 -0500, "lists-md-support@mdaemon.com (Voinea Ilie)" <lists-md-support@mdaemon.com> wrote:
We have a lot of sessions that are ending with the error Socket error 10054 - Connection was reset by the other side!
How can I identify what kind of problems are causing this error?

Mdaemon(64) 12.5.1
Thank you!


View/reply at Socket error 10054 - Connection was reset by the other side!
--MD-SUPPORT--------------------------------------------------------------
This list is for questions and discussion about MDAEMON. To unsubscribe 
from this mailing list send an email to md-support-unsubscribe@mdaemon.com .
--POWERED BY MDAEMON!-----------------------------------------------------

--------------------------------------------------------------------------
These forums are provided by MDaemon Technologies for user-to-user 
support and discussion.  MDaemon staff members may participate in the 
forums periodically but please recognize that this is not the official
method of receiving technical support. To receive personal technical 
support please use the form here:
http://www.mdaemon.com/Support/RequestSupport/
--------------------------------------------------------------------------

--MD-SUPPORT--------------------------------------------------------------
This list is for questions and discussion about MDAEMON. To unsubscribe 
from this mailing list send an email to md-support-unsubscribe@mdaemon.com .
--POWERED BY MDAEMON!-----------------------------------------------------

--------------------------------------------------------------------------
These forums are provided by MDaemon Technologies for user-to-user 
support and discussion.  MDaemon staff members may participate in the 
forums periodically but please recognize that this is not the official
method of receiving technical support. To receive personal technical 
support please use the form here:
http://www.mdaemon.com/Support/RequestSupport/
--------------------------------------------------------------------------

Replies to this message
  • Voinea Ilie (Jan 17, 2022 10:51 am)
  • Voinea Ilie (Jan 18, 2022 6:31 am)


  • Voinea Ilie - Jan 17, 2022 10:51 am (#2 Total: 4)  

     

    Photo of Author
    Voinea Ilie
    Newbie
    Newbie
    Posts: 14
    Replying to: Arron Caruth (Jan 17, 2022 8:19 am)
    Can you confirm the version of MDaemon you are using?&nbsp; There is not a 64 bit version of MDaemon 12.5.1,...

    Sorry, my typo, Mdaemon v21.5.1

    Voinea Ilie - Jan 18, 2022 6:31 am (#3 Total: 4)  

     

    Photo of Author
    Voinea Ilie
    Newbie
    Newbie
    Posts: 14
    Replying to: Arron Caruth (Jan 17, 2022 8:19 am)
    Can you confirm the version of MDaemon you are using?&nbsp; There is not a 64 bit version of MDaemon 12.5.1,...

    Mdaemon(64) v21.5.1

    The error occurs in multiple sessions, both SMTP(in) and IMAp
    Sometimes the sessions are closed, the transfer is not completed, sometimes the messages are transferred.
    I will write below some examples from the logs. Not all of them have explanations related to the end of the sessions, before the errors appears:

    Wed 2022-01-12 10:18:56.426: * Socket error 10054 - Connection was reset by the other side!
    Wed 2022-01-12 10:18:56.426: SMTP session successful (Bytes in/out: 105762/669)

    Wed 2022-01-12 10:17:47.211: * Socket error 10054 - Connection was reset by the other side!
    Wed 2022-01-12 10:17:47.211: SMTP session terminated (Bytes in/out: 2949/6551)
    This last closed session is from an outlook.com server, the error in the unsent message logs is: Reason: [{LED=450 4.4.318 Connection was closed abruptly (SuspiciousRemoteServerError)}



      (newer msg:1)All MessagesOldest ItemsOlder ItemsNewer ItemsNewest Items



     Content:

    Read New | Search

     Guest:

    Email to Admin



    You are visiting as a Guest user.