Thanks for reminding me of the Web Monitor. I recall that vaguely.

 

Next it happens – if it ever should, I will try disabling Declude and Imail 
services first to see if anything manages to clear up the symptoms.

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Bilbee
Sent: Wednesday, May 30, 2007 12:59 PM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] Winsock Cleanup
Sensitivity: Personal

 

What version of Imail. A few years back I reported a problem to IPSwitch that 
the monitor application, part of IMail, would suck up all the available TCP 
ports on the server. I narrowed it down to the web monitor. Try turning off the 
web monitor or better yet IMail monitor altogether and see if your problem goes 
away. As far as I know they never fixed the issue, or at least I never saw the 
fix in any of the release notes.

 

We are now on SmarterMail and do not miss all the denials when reporting bugs 
that IPSwitch would throw out.

 

 

Kevin Bilbee

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andy Schmidt
Sent: Wednesday, May 30, 2007 6: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.

Reply via email to