Currently Qpopper has a timeout between commands, but there is no timeout when the server is sending a message to the client.
If I'm receiving a long email and suddently my inet connection is closed, two things can occur: a) The next datagram from the server will be answer by the network using an ICMP "host unreachable" or similar. Current Qpopper correctly detects this fact and closes the connection. b) The next datagram from the server will simply banish. TCP retransmits and the following datagrams also banish. A black hole... In this situation QPOPPER hasn't any timeout, so the server will be blocked forever. I think QPOPPER should use timeout when sending data to the client, in order to recognice "b" scenary. So qpopper would have the opportunity to cleanup the mess. -- Jesus Cea Avion _/_/ _/_/_/ _/_/_/ [EMAIL PROTECTED] http://www.argo.es/~jcea/ _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ _/_/_/_/_/ PGP Key Available at KeyServ _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz
