Re: [IMail Forum] Outbound Mail Failing - send error 10054

[Darin Cox]

Title: Message

Ahh...gotcha.  Thanks for the clarification. Darin.     ----- Original Message ----- From: Eric Shanbrom [Ipswitch] To: [EMAIL PROTECTED] Sent: Sunday, October 31, 2004 3:11 PM Subject: Re: [IMail Forum] Outbound Mail Failing - send error 10054 One way would be to be in the middle of a refresh when the server is trying to send info to the browser....notice these are send errors so the server is trying to send info on a socket that is "Closed by Peer (10054 by definition)".. There are also many server side initiated communications when a session is live...Sorry for not being clear..   Eric S     ----- Original Message ----- From: Darin Cox To: [EMAIL PROTECTED] Sent: Sunday, October 31, 2004 12:55 PM Subject: Re: [IMail Forum] Outbound Mail Failing - send error 10054 ES> If in the Web logs, then it's not too much of a problem as you will see toms of these. ES> The cause is usually someone closing their browser without logging off. Web messaging ES> has refreshes built into most of the pages and not logging off keeps the session ES> open. When the refresh tries to be sent it is then that you will get these.   How would that be???  Refreshes are initiated by the browser, not the server.  So if the user closes the browser (whether or not they logged off) no more refreshes are initiated. Darin.     ----- Original Message ----- From: Eric Shanbrom [Ipswitch] To: [EMAIL PROTECTED] Sent: Sunday, October 31, 2004 10:37 AM Subject: Re: [IMail Forum] Outbound Mail Failing - send error 10054 It depends on which log you are seeing these in.   If in the Web logs, then it's not too much of a problem as you will see toms of these. The cause is usually somone closing their browser without logging off. Web messaging has refreshes built into mosst of the pages and not logging off keeps the session open. When the refresh tries to be sent it is then that you will get these.   If in the POP3/IMAP log. this is also the case, when clients are closed prematurely.   If in the SMTPD log this is usually an indication of a higher order problem as this should be a continuous session until complete. The error itself, 10054, is a winsock error being reported by the TCP Stack. Historically these occur much more with Gigbit NIC's (especially onboard, Intel chipsets). One thing, on top of disabling the power management, I have seen have a positive effect on this is to lock the NIC speed to 100mb Full Duplex. Be careful if using Intel NIC's with the Broadcom NetXtreme drivers as in some cases this will lock zthe NIC at 10mb Half Duplex. It is also extremely important to use the manufacturere's driver instead of the native windows driver   Hope this helps Eric S ----- Original Message ----- From: Bill Foresman To: [EMAIL PROTECTED] Sent: Sunday, October 31, 2004 9:59 AM Subject: RE: [IMail Forum] Outbound Mail Failing - send error 10054 anyone have an idea about this problem? I've got some of these in our logs as well but we've never had anyone mention a problem. Bill Foresman Matrosity Hosting www.matrosityhosting.com Office: (850) 656-2644 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wolf Tombe Sent: Sunday, October 31, 2004 8:28 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [IMail Forum] Outbound Mail Failing - send error 10054 I�ve just configured my new mail server and am having trouble getting SMTP to send outbound messages (it received inbound e-mail fine).  I�m running iMail 8.13 with Declude 1.81 and Windows 2003 Enterprise Server on a Dell 2850 PowerEdge server with two processors, 2Gb RAM, running RAID 1 with 140Gb available disk space and Two Intel 1Gb NICs.  The problem I�m having is that ALL outbound messages are failing.  The logs show the following errors:   10:28 08:00 POP3D  (00000D70) send error 67.101.20.130 10054 10:28 08:00 POP3D  (00000d70) 67.101.20.130 connection reset   20041028 184600 Socket Error - 192.168.1.2 Error while writing sockect due to error 10054 or malicious connection type. 20041028 184600 Socket Error - 192.168.1.2 Error while writing sockect due to error 10054 or malicious connection type. 20041028 184600 Socket Error - 192.168.1.2 Error while writing sockect due to error 10054 or malicious connection type.   I�ve searched the Ipswitch knowledge base and found the articled at http://support.ipswitch.com/kb/IM-20020812-DM01.htm and have changed the power management settings on both the NICs as specified; but the problem still persists.   Additionally, when I reboot the server, upon startup ALL messages that are still in the outbound queue are processed and successfully sent, but any subsequent messages fail with above problem and are held until the server is again rebooted.   Any help or advice will be greatly appreciated!