On Thursday, December 25, 2003, Marck D Pearlstone wrote... > I've seen reports of POP3 stalling at 100%. I'm seeing something > else / worse.
> Once in a while, a mail check fails to start. It fails to start > catastrophically. I don't know why - maybe there's a collision in > the LAN here The TCP/IP protocol is designed to handle things like this... if it's being caused by collisions, then TB has bigger issues. > (they happen - I should fix it, but I have more pressing things to > do - a "builder's house" and all that), maybe the server stutters > (it's a bit under-powered for what it needs to do).. whatever. One > way or another, something goes wrong during the initial connect > phase prior to message collection. Even a server stutter really shouldn't cause any issues... the client should be able to handle it... if the server reports and error, the client should be able to report the error, and retry later, not hang itself indefinitely. Wasn't there a new timeout option added recently? I thought I saw mention of it, and vaguely remember seeing it too, but I cannot find it now... if you still have it (or it even exists), what is yours set to? > Having stalled at this point, that's it for that account. There's no > timeout. There's no recovery. There's no abort. Nothing will make > that task recover other than a task manager enforced eviction. Often > I don't even notice that the account has been locked out until two > hours later. Or more. The connection centre shows the account trying > to connect still. If I abort or delete the task, the connection > centre clears the task from view but clearly it is still open in > there somewhere; the connection centre remains open and TB refuses > to exit. Can you pinpoint things going on? Like mail accounts checking at the same time? Is there anything in your server logs? Do you even see that failed connection attempt? Have you considered running ethereal (http://www.ethereal.com/) to watch POP3 connections and see if anything pops up (pun not intended)? Ethereal will be useless if you do POP3 over SSL ;) > There should also be timeout protection on all phases of a > communications session, so the "locked out" issue shouldn't arise. I could have swore one was put in. But you have to be really careful when doing this kind of thing.. especially when it comes to networks and proxy services. The company I used to work for had Wingate as a proxy server (that was before I got my hands on it)... one person used to get huge mails (around 100MB) all the time, but Outlook would timeout because the wingate proxy was handling conversations with the server, while not talking back to the client... then once the connection between wingate and the server was done, the whole bunch was then dumped to the client (an interesting way of doing things I must say). But I do agree that one should be put on the connection side of things, or the login phases, and exit phases. -- Jonathan Angliss ([EMAIL PROTECTED]) Jesus saves sinners and redeems them for cash and valuable prizes.
pgp00000.pgp
Description: PGP signature
________________________________________________________ Current beta is 2.03 Beta/24 | "Using TBBETA" information: http://www.silverstones.com/thebat/TBUDLInfo.html
