[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 77862] kio_imap processes hang when connection status changes
From:       Maurel <guy-kde () maurel ! de>
Date:       2010-11-10 17:28:16
Message-ID: 20101110172816.4EFDF74606 () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=77862





--- Comment #87 from Maurel <guy-kde maurel de>  2010-11-10 18:28:06 ---
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.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]