Bug 311996 - IMAP quota (folder colour) isn't automatically refreshed
Summary: IMAP quota (folder colour) isn't automatically refreshed
Status: RESOLVED FIXED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: GIT (master)
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Christian Mollekopf
URL:
Keywords:
: 314500 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-12-20 16:43 UTC by Pal Körössy
Modified: 2013-11-28 11:27 UTC (History)
6 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 Pal Körössy 2012-12-20 16:43:18 UTC 
If an IMAP account is over quota, inbox and all its sub-folder turns into red.
The problem is that they don't automatically turn black after deleting enough messages and account is under notification-limit again.
"Download messages" and "Update folder and its subfolders" don't help, only going to the "Quota" tab on "Folder properties" dialog does the trick.
Also a problem is that the subfolders don't turn black, I have to repeat going to the "Quota" tab on "Folder properties" dialog again to make them black.

Reproducible: Always
Comment 1 Laurent Montel 2013-02-06 08:54:11 UTC 
*** Bug 314500 has been marked as a duplicate of this bug. ***
Comment 2 Philipp Woelfel 2013-03-17 22:39:13 UTC 
I can confirm this on openSuSE 12.3 with KDE 4.10
Comment 3 Philipp Woelfel 2013-03-17 22:51:03 UTC 
Moreover, after moving a "red" folder to a different account I cannot make it "black" at all. Even if I click on "Folder properties" and then the "Quota" tab, it remains red.
Comment 4 Laurent Montel 2013-05-21 13:19:03 UTC 
Move by dnd folder doesn't refresh quota. Bug knows (same for acl).
It's not an imap resource bug but an akonadi bugs.
Comment 5 Kevin Ottens 2013-11-16 07:33:33 UTC 
The IMAP resource has a new maintainer, reassigning to him.
Comment 6 Christian Mollekopf 2013-11-28 11:27:48 UTC 
I think this is fixed by now since metadata is now updated regularly.

The necessary patches are currently in master only:
972cbee
a4452f7