Thanks Dave.
So: a) Does the scenario that I described (which was not specific to IMAIL or Declude but also effected other TCP/IP applications on that machine) still "fit the bill"? b) What if I were to turn on WinSockCleanUp just to be safe? What risk do I take? What is the negative impact? What will "resetting the winsock" cause with respect to other TCP/IP applications? Performance impact? Stability impact? (After all, if there IS no impact, why would it not be ON by default)? c) Imail Bug: Has Ipswitch acknowledged that bug, e.g., they are fixing it? Or is that something that we still need to take up with them? That option is quite old and IMail has seen several new versions since then. So I wonder! From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Barker Sent: Wednesday, May 30, 2007 10:11 AM To: declude.junkmail@declude.com Subject: RE: [Declude.JunkMail] Winsock Cleanup Sensitivity: Personal Some installs of IMail had an issue where there winsock would cause problems for network functionality, this was a bug in Imail, it seemed by stopping smtp32 service of Imail resolved the issue. Declude uses the winsockcleanup to reset the winsock to deal with this. winsockcleanup kicks in when the \proc directory is empty or reaches 0 files Decludeproc will reset the winsock. David Barker Director of Product Management Your Email security is our business 978.499.2933 office 978.988.1311 fax [EMAIL PROTECTED] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andy Schmidt Sent: Wednesday, May 30, 2007 9:34 AM To: declude.junkmail@declude.com Subject: RE: [Declude.JunkMail] Winsock Cleanup Sensitivity: Personal Hi, Does anyone have any comment on the attached email (possibly even Declude personnel)? I checked the mailing list archive - and it seems to imply as if the WinsockCleanup is specific to DNS problems and results in queues filling up. In my example, Imail and Declude didn't seem to be filling up queues. The couldn't because TCP/IP would not let any inbound connections go through. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andy Schmidt Sent: Friday, May 25, 2007 4:03 PM To: declude.junkmail@declude.com Subject: [Declude.JunkMail] Winsock Cleanup Sensitivity: Personal Hi, What are the symptoms related to Winsock Cleanup? After running fine for 2 months or so (except for occasional reboots for Hotfixes), the mail server stopped working on the TCP/IP level. It didn't respond to Ping from the outside. You could log into the console and Ping to itself. There was also some notice about a Browser Election during the outage - so it seems as if there was still communication on the Ethernet layer (such as LAN segment broadcasts). A reboot resolved the issue. Does this sound like the situation that this option is intended to fix: #WINSOCKCLEANUP some customers had issues related to their network stack causing loss of functionality for basic #network operations.The default for this directive is OFF #WINSOCKCLEANUP OFF Is it consistent with this problem, that the server might have worked fine for a few months and had been rebooted just a few days prior - and to suddenly display this behavior? What's the impact if that is set to "ON" unnecessarily? Best Regards, Andy --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
