Bug 150638 - kmail mail check freeze on imaps account if imap server is restarted
Summary: kmail mail check freeze on imaps account if imap server is restarted
Status: RESOLVED FIXED
Alias: None
Product: kmail
Classification: Applications
Component: IMAP (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-09 19:36 UTC by p92
Modified: 2010-01-11 00:36 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
showing the hung process at bottom right (128.30 KB, image/png)
2007-10-09 19:40 UTC, p92 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description p92 2007-10-09 19:36:08 UTC 
Version:           1.9.6 (enterprise 0.20070907.709405) (using KDE 3.5.7, Kubuntu (gutsy) 4:3.5.7-1ubuntu15)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.22-13-generic

I have an imap account configured with SSL encryption.

This is working fine until my imap server is stopped each night (for backup purposes) then restarted. Kmail issues the message that the imap account has been disconnected. But then I am unable to read the inbox folder again. When I try to open it kmail displays that it is receiving the content of the folder and be patient. Indicator of progress at the bottom right shows: account check : 100% and that's all.

I can change to another folder on the imap server and the content is shown. 

There is always an instance of the inbox folder checking that is hung and prevent it from beeing shown.
Comment 1 p92 2007-10-09 19:40:22 UTC 
Created attachment 21782 [details]
showing the hung process at bottom right
Comment 2 p92 2007-10-09 19:41:51 UTC 
the only way to recover is restarting kontact
Comment 3 p92 2007-10-09 20:16:19 UTC 
humm seems a duplicate of #76872 still occuring in 
KMail Version 1.9.6 (enterprise 0.20070907.709405)
Comment 4 Björn Ruberg 2010-01-11 00:36:23 UTC 
Bug #76872 is fixed so this is probably too. Please report if not.