Hello Marck, in [EMAIL PROTECTED]">mid:[EMAIL PROTECTED] was written:
>> then that global variable (probably a boolean) is not reset to the >> state reporting that it is not doing anything. MDP> I think that the client side Socket connection is left open and MDP> until it is flagged as closed TB won't open a new one. But how to tell? 'netstat' didn't show me an open socket neither on my client nor on my server when I wan into that trouble. MDP> It may be worth a BugTraq entry. It never happens to me (Win2k Pro, MDP> LAN connect to MDaemon server, polling for mail every 1 minute MDP> (that's right - sixty seconds!). But it happened (not within last 2 weeks, OK) to me on a LAN connection. 100MBit switched network. No other traffic, just my workstation and my server switched on (and the router of course). MDP> I think it requires a POP server on the other end that is capable of MDP> losing the connection. MDaemon doesn't appear to be <g>. I'd be glad if that would be an explanation, but I'm unhappy to tell you: my daemons ran without any error message for weeks and month, albeit TB! hung several times. >> Try seeing if you can terminate the connection in an abnormal way, >> such as 95% the way through picking up the last message, >> disconnect... *shrugs*... it may have the same effect, or TB! may >> know how to handle that event properly. MDP> That would be an interesting exercise. And it was done. If I shut down the daemon listening to port 110 the normal TCP mechanisms stepped in and the connection was terminated with an error message, as it is supposed to be. So ... anybody any other interesting riddles to go through? I'm happy to play them and present the results, but I wasn't able to figure out what causes this, all my knowledge about networks, servers, daemons, debugging them and network sniffing didn't help me yet to find the origin of this casual hangings. I can only guess this is an error in socket component used in The Bat!, but of course I can't prove it. BTW: I can't for the same reasons I don't know why my local SSL doesn't work anymore: lack of information and debugging information .... :-/// P.S.: Jonathan wrote: > I'm in arms reach of one of my mail servers Me too. It could get a slap on it's CD-Drive if it would refuse to work. Happily it does not even come to the idea of doing so :-) -- Regards Peter Palmreuther (The Bat! v1.62/Beta1 on Windows 2000 5.0 Build 2195 Service Pack 2) Whatever is not nailed down is mine. What I can pry loose is not nailed down. ________________________________________________ Current version is 1.61 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
