Version: (using KDE 4.1.2) Compiler: various OS: Linux Installed from: Gentoo Packages Steps to reproduce: 1. Start kmail 2. Open IMAP folder 3. Disconnect internet connection 4. Wait until Time-Out -> An error message from kmail will appear 5. WAIT SOME MINUTES 6. Click the message away ---> The imap folder is "frozen": No messages appear etc. Other imap-folder (also sub-folder of the frozen one) are ok. To access the frozen folder again, kmail must be restarted.
The problem also exists in 3.5.x
I can confirm that. It has happened to me many times as well, but I had not identified the reason. Now that I read this bugreport I realize that there was indeed a connection timeout before the imap freeze all the times that it happened.
Another info: It also happens if kmail has no internet connection at startup. Then an error message is shown. If I confirm the message immediately, then everything is fine as soon as a connection to the IMAP server is possible. If I wait some minutes before clicking the error message away, the folder is frozen. This is an very annoying bug, because it happens quite often in my usual "workflow": For example, on my laptop it is often the case that I network-manager ask for a password from kwallet for WLAN access and kmail is startup automatically. So both WLAN configuration and kmail (also waiting for kwallet to be opened) are started synchronously. This results in kmail to fail, because WLAN configuration is still in progress. Very often I start something else in parallel, e.g. a web browser, so I ignore the error message from kmail. When I want to access my mail later, this is not possible.
*** Bug 173506 has been marked as a duplicate of this bug. ***
I have the same issue, and I usually have to restart or kill kmail (or kontact) to resolve this issue. This happens to me all the time, especially since I use suspend to ram a lot and that knetworkmanager does no reconnect immediately. Maybe there should be some kind of mechanism that detects whether the computer is online or not.
*** This bug has been marked as a duplicate of bug 77862 ***