Version:           1.13.5
OS:                Linux

For some inexplicable reason, kmail thinks that a TCP connection is the most reliable thing in the world, so it totally does not handle the case when the connection goes down and the TCP connection has to be established again.
The only thing to do when this happens is to RESTART KMAIL.
Meaning that if one is using a wireless connection and the AP isn't so close, or if i decide to suspend my laptop and open it again after 3 hours, kmail will have to be restarted in order to work again.
This is quite annoying, and it has been like that for ages.

Is it really that difficult to add a connection timeout or even notice that if a  
read(socket,&buffer,b_size) is returning 0 then the connection is LOST and further attempts of reading data from that connection are going to fail?
Honestly, i don't think it should be that hard and time consuming task, if it is then there is something wrong with the architecture of the software itself.

Yes this bug is duplicated, no i don't care. I think making things work as expected is most important than adding fancy features.

I am reporting it as a crash because a software that needs kill -9 in order to work again, is more close to a crash rather than to a normal bug.

Bye

Reproducible: Always




OS: Linux (x86_64) release 2.6.35.7-calipso
Compiler: cc