Bug 100478 - KMail does not recover from IMAP issues, it cannot be interrupted
Summary: KMail does not recover from IMAP issues, it cannot be interrupted
Status: RESOLVED DUPLICATE of bug 77862
Alias: None
Product: kmail
Classification: Applications
Component: IMAP (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-28 20:54 UTC by Dominik L. Borkowski
Modified: 2007-09-14 12:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dominik L. Borkowski 2005-02-28 20:54:58 UTC
Version:            (using KDE KDE 3.4.0)
Installed from:    Compiled From Sources
Compiler:          gcc 3.3.4 
OS:                Linux

Kmail seems to be unable to recover from any IMAP connectivity errors. Once it looses connection to IMAP, the status bar displays the progress at halt, and the little red icon in that bar does not interrupt this process. At this point the only solution left is to restart kmail. This has been happening in kde 3.2, 3.3 and it seems to exist still in 3.4.0rc1.
Comment 1 Carsten Burghardt 2005-03-03 10:03:10 UTC
There has been a lot of improvement for 3.4 in this case so it would be good if you could explain how to reproduce this.
Comment 2 Dominik L. Borkowski 2005-03-03 15:08:55 UTC
The most common way that I, among others, have been able to produce this bug is by moving our laptops between networks. I assume that the easiest way to do it with a stationary machine would be to drop the network interface and bring it back up eventually, or by changing the ip.

Following are two of the ways that I can always result in kmail hanging, and never being able to interrupt accessing the imap server:

a) I launch kmail, connect to our imap server. I suspend the laptop, take the laptop to another network, start the laptop. Kmail will show which mailbox it's trying to access, and never let you interrupt it.

b) When my vpn client dies and that results in lack of connectivity to the imap server, the situation happens again.

The IMAP server in question is uw-imap. 
Comment 3 paul.leopardi 2005-03-14 23:24:45 UTC
I can confirm similar, if not identical, using Kmail 1.8 (Using KDE 3.4.0 Level "a" SUSE 9.2 UNSUPPORTED).

To reproduce (requires DSL Internet connectivity or similar), start Kmail, connect to IMAP server by displaying an IMAP folder, stop KInternet, wait for timeout, click continue on timeout dialog box, display IMAP folder.

Logs show (eg.):
libkdepim: ProgressItem::cancel() - Checking account: maths
kmail: processNextCheck, remaining 1
kmail: account maths finished check
kmail: connections to server mail.maths.unsw.edu.au now 1
kmail: for host mail.maths.unsw.edu.au current connections=1 and limit is 0
kmail: connection limit reached: false
kmail: processing next mail check for maths
kmail: processNewMail true,status=2
kmail: KMFolderImap::processNewMail - waiting for connection: drafts
kmail: KMFolderImap::checkValidity of: /INBOX/
kmail: CheckValidity - waiting for connection
kmail: KMFolderImap::processNewMail - waiting for connection: Oxfam
kmail: KMFolderImap::processNewMail - waiting for connection: saved-messages
kmail: KMFolderImap::processNewMail - waiting for connection: sent-mail
kmail: check mail started - connections for host mail.maths.unsw.edu.au now is 2
kmail: account maths busy, queuing
kmail: processNextCheck, remaining 1
kmail: for host mail.maths.unsw.edu.au current connections=2 and limit is 0
kmail: connection limit reached: false
libkdepim: ProgressItem::cancel() - Checking account: maths
kmail: account maths busy, queuing
kmail: processNextCheck, remaining 3
kmail: for host mail.maths.unsw.edu.au current connections=2 and limit is 0
kmail: connection limit reached: false
kmail: for host mail.maths.unsw.edu.au current connections=2 and limit is 0
kmail: connection limit reached: false
kmail: for host pop3.unsw.edu.au current connections=0 and limit is 0
kmail: connection limit reached: false

Comment 4 Matt Douhan 2005-05-28 11:04:39 UTC
Myself and Till Adam spent an entire day working on this for whatbecame shipped with kde 3.4.1, and at the end of the day, we could start a (s)IMAP synch, yank the cables wait for timeout reinsert the cable and clock continue or stop, and both cases worked.

I could move a laptop between two different subnets, starting kontact on one subnet, suspend the laptop and move to another, get a new IP address, stop the synchs or click continue and they would stop and proceed respectively.
Comment 5 Tarek Loubani 2005-06-02 06:57:56 UTC
I have experienced this issue for a very long time, and things seem generally harder to break with 3.4.1, but I still occasionally manage. What I do is the following:

1. Click "check mail"
2. Suspend for a reasonable amount of time (5min?)
3. Come back from suspend
4. Note that email is still "checking", but not progressing
5. Hit "cancel" (red X) button

What happens then is that all subsequent "check mail" attempts fail. navigating the dropped imap session folders fails. If I right-click on the imap folder and click "subscription", Kmail faults out.

tarek : )
Comment 6 Matt Douhan 2005-06-12 21:23:03 UTC
I suspended my laptop for at least 10 mins, and come back I could cancel the prog bras and restart the synch without any issues.
Comment 7 Sebastien Renard 2005-06-20 17:07:47 UTC
Hello,

I have the same issue (kmail: account myAccount busy, queuing) here but with POP3.
It only occurs when I use pre-command (starting an ssh tunnel to pass through proxy for instance). Sometimes it fails and then I cannot pop mails. No message error on kmail side, just no mail and this message in .xsession-errors (account busy, queuing).

The only way to recover is to stop and start kontact.

I have this problem since KDE 3.3.x. I am using 3.4.1 and the bug is still there.

Regards
Comment 8 Thomas McGuire 2007-05-12 14:34:09 UTC

*** This bug has been marked as a duplicate of 77862 ***