Yeah, I spoke too soon

at 6 days 9 hours earlier today the 10055 out of buffer space error appeared again.

Doogle, I started thinking about your comments in an earlier post where the internal buffers could be the problem.

I ran some searches on the net and came up with this statement from Microsoft:

"This behavior can occur because computers that run Microsoft Windows NT clients and use excessive numbers of ports (more than 3,976 simultaneously) may run out of ports before TCP/IP releases closed connections. The TCP/IP-state computer dictates that when a connection is closed, the connection is not released until two maximum segment lives (MSLs) have passed. This state is defined as the Time-wait state. Since one MSL is defined as 120 seconds, it takes four minutes for a closed connection to be released in TCP/IP. "

Since it takes 4 min to actually close the connection and the pop3 connect fires every 2 min, the buffers may be getting filled up and not released in time for the next connect.

In this article http://support.microsoft.com/default...b;EN-US;149532, it prompts to change the TcpTimedWaitDelay state from the default of 2 min to something lower like maybe 30 sec.

Another option may be to code pop3 connect to only connect once every 5 min (which I can certainly live with if it resolves this issue). This would then give enough time for windows to naturally close its connection thus clearing the Time_Wait state.

What do you think?

Patrick