[Kde-pim] Let us close the bug 77862 we cannot solve.

[Guy Maurel]

Hello!

I have made an analyse of the problem, one can read at the 
kde-pim@ on 2010-10-31. The bug 77862 is:
- not an IMAP problem, all other protocols would have it too,
- not a kmail problem, all other front-end mail-tool also,
- not a KDE  problem.
This is an IP-v4 problem we cannot solve. All applications which have 
(long time) connections could have the problem at any time.

Let me quote a white paper from "www.isode.com".
    http://www.isode.com/whitepapers/imap-idle.html

Beside my analyse they publish the same :

"... Another practical problem is that current phone networking technology 
will lose IP network connectivity from time to time, and this will need to be 
automatically re-established, and the IMAP connection re-established if this 
is lost due to a long network failure. ..."

We can only propose some workarounds. 
Even my proposals were workarounds. The best one is to change the 
timeout at waitForRead, as proposed, a long time ago, by Robert Huitl on 
2009-10-25
   https://bugs.kde.org/show_bug.cgi?id=77862#c48

and improve the errorhandling after that.

As David Faure notices at Comment #85, the situation at airport wifi is not 
very stable. The timeout should not be too short. As the connection comes 
again, we might get the same IP-address as before.
I propose a value of 20 seconds.
-- 
guy
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/