Bug 163268

Summary:	local unsubscribe info is not persisted quickly enough
Product:	[Applications] kmail	Reporter:	Thomas Zander <zander>
Component:	disconnected IMAP	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED WORKSFORME
Severity:	grave	CC:	lemma, netz
Priority:	NOR	Keywords:	triaged
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:

Description Thomas Zander 2008-06-05 13:59:00 UTC

Version:            (using Devel)
Installed from:    Compiled sources

In kmail trunk I locally unsubscribed to various mail folders and then continued to work with kontact.  After a couple of minutes I managed to crash Kontact and subsequently restarted it.

Some time later my dimap folder hit its auto-sync timeout and started syncing.  From the fallout I gather the following happened;
the syncing software noticed the missing folders but did not notice that I had enabled local-subscriptions and marked those as unsubscribed.  The effect is that the folder was created locally and the folder content was removed remotely.
Effectively loosing all my mail.

Configuration options like subscriptions should be persisted immediately IMO.  Also the kde3 kind of sanity detection that would have cough this seems to have been lost on porting.

Comment 1 Thomas McGuire 2008-06-07 20:17:35 UTC

SVN commit 818102 by tmcguire:

Store local subscription info immediately. Might help with bug 163268

CCBUG: 163268


 M  +4 -0      imapaccountbase.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=818102

Comment 2 Thomas McGuire 2008-06-07 20:21:40 UTC

I can not reproduce this.
I tried the following: I unsubscribed from an DIMAP folder, then killed KMail.
The config didn't have the information that the folder was unsubscribed yet, but the maildir cache of that folder was already removed.

Then I restarted KMail, and synched the account. The folder reappeared, will all messages still there (though I only had 1 message in there for testing).

So in your case something else must have happend, it would be very helpful if you find out what it was.

Nevertheless I added a config sync after changing local subscription.

Comment 3 Thomas Zander 2008-06-07 21:05:40 UTC

On Saturday 7. June 2008 20:21:41 Thomas McGuire wrote:
> So in your case something else must have happend, it would be very helpful
> if you find out what it was.

Thanks for investigating, these things are not easy to check, I know :)

I can't think of anything else that would have happened, I was configuring the 
app (as I stated in my initial description).
Maybe the point of me enabling the local subscription for the account is 
relevant?  Since that may also not have been saved to the config file.

Other than that, sorry, I can't help further.

Comment 4 Jan Essert 2009-04-04 17:06:27 UTC

I cannot reproduce this here with kmail 1.11.1 on kde 4.2.1. Since this is over half a year old and there was a related commit, could you tell us whether this has occured again? If yes, perhaps you have additional information?

Comment 5 Thomas Zander 2009-04-05 00:33:58 UTC

I have not really been able to crash kmail since ;)
So I can't confirm or deny that the problem is gone.

I won't be sad if the maintainers think this bug can be closed, though.

Comment 6 Jaime Torres 2009-12-06 13:03:39 UTC

Please reopen if this happens again.
I've not been able to reproduce it with kmail from 4.4 beta 1.