Bug 283513

Summary:	list of IMAP folders out of sync
Product:	[Applications] kmail2	Reporter:	Silver Salonen <silver.salonen>
Component:	folders	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	amantia
Priority:	NOR
Version:	4.7
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Silver Salonen 2011-10-07 06:36:56 UTC

Version:           4.7 (using KDE 4.7.1) 
OS:                Linux

I did not use KMail for a while now and I've re-organized my IMAP-folders a bit. I thought I'd try KMail again, but now KMail shows my IMAP-account's folders out-of-sync - folders I've moved under some other folders are still in their original place and not where they are supposed to be etc. When I check the account's serverside subscription, it shows correct list there, but well.. how can I get THAT list to be reflected in the folder list?

Reproducible: Didn't try

Steps to Reproduce:
Manage IMAP-account's folders from another application and see whether KMail will show the updates.

Actual Results:  
KMail's folder list goes out of sync

Expected Results:  
KMail folder list should be updated to the current state of the IMAP account

Comment 1 András Manţia 2012-02-11 23:57:30 UTC

Have you synched the account (right click on the account folder or using Check mail)?

Comment 2 Silver Salonen 2012-02-12 09:31:47 UTC

Yes, I did.

Comment 3 Silver Salonen 2013-02-06 07:56:24 UTC

So, any developers interested in more info? I've eagerly waited not to touch my setup, so I wouldn't "break" this buggy behavior and could give more information :)

Comment 4 Denis Kurz 2016-09-24 18:21:24 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.

Comment 5 Denis Kurz 2017-01-07 22:14:55 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.