Hi TB Beta list members, 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 (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. 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. I'm set up to leave mail on the server for 1 day. I don't know if that's relevant. Whether or not this issue can be reproduced or fixed I don't know. What is clear to me is that I need a more orderly way to leave TB when there are "unfinished tasks". I need an extra option of "Ignore and exit anyway" for any time something goes wrong in the comms. There should also be timeout protection on all phases of a communications session, so the "locked out" issue shouldn't arise. -- Cheers -- .\\arck D Pearlstone -- List moderator TB! v2.03 Beta/22 on Windows XP 5.1.2600 Service Pack 1 '
pgp00000.pgp
Description: PGP signature
________________________________________________________ Current beta is 2.03 Beta/22 | "Using TBBETA" information: http://www.silverstones.com/thebat/TBUDLInfo.html
