Bug 323625 - Add folder creates folder on imap server but doesn't show in kmail2
Summary: Add folder creates folder on imap server but doesn't show in kmail2
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: folders (show other bugs)
Version: 4.11
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-17 07:57 UTC by Ruchir Brahmbhatt
Modified: 2017-01-07 22:48 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ruchir Brahmbhatt 2013-08-17 07:57:40 UTC 
OS: opensuse 12.3 x86_64
KDE: 4.11 from KDE:Release:4.11 repository
Account: Disconnected IMAP Gmail

Creating new folder doesn't immediately reflect on kmail2, its done on server though.

Reproducible: Always

Steps to Reproduce:
1. Right click  main account.
2. Select add folder.
3. Enter folder name. ( I tried 3 times with names 00001,00002 and 00003)
Actual Results:  
Folder created on server but not showing up in kmail2. I can see all 3 folders I created in gmail but not in kmail2 until restart.

Expected Results:  
Folder should be created and shown immediately in kmail2.
Comment 1 Martin Koller 2013-11-12 20:28:31 UTC 
I can confirm this with KDE 4.11.3 when I create a toplevel folder.
When creating a subfolder, kmail shows the new folder immediately
Comment 2 S. Bryant 2013-11-27 12:52:57 UTC 
This looks like a duplicate of bug #266666.
Comment 3 Denis Kurz 2016-09-24 18:09:04 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 4 Denis Kurz 2017-01-07 22:48:07 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.