Bug 277662 - Previously disabled/empty folder in an Imap resource does not update when server-side properties change.
Summary: Previously disabled/empty folder in an Imap resource does not update when ser...
Status: RESOLVED WORKSFORME
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Christian Mollekopf
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2011-07-12 22:22 UTC by George Brooke
Modified: 2018-10-27 03:38 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description George Brooke 2011-07-12 22:22:00 UTC
Version:           unspecified (using KDE 4.6.4) 
OS:                Linux

I have an Imap account with plus addressing enabled and which is setup to automatically sort incoming emails into folders based on the +address - so +kde.bugs will end up in the Imap folder /kde/bugs
If these folders don't exist then they are created as email arrives.

If an email arrives for +kde.bugs and /kde does not exist it is created as an empty folder which appears in kmail2 as a greyed-out folder which has the akonadi ACLs (viewed with akonadiconsole) all unchecked and the Attributes;
AccessRight | <blank>
noselect    | 1

/kde/bugs is created with the same ACLs and similar attributes to the other mail folders and then behaves normally in kmail2.

If an email then arrives for +kde the folder is not updated to display the emails, even after reloading the whole imap resource.
To make the emails appeare the ACLs must be changed to match the other mail folders and the attributes both deleted. Once this is done emails are loaded correctly.

Reproducible: Always

Steps to Reproduce:
See details


Expected Results:  
See details
Comment 1 Kevin Ottens 2013-11-16 07:30:00 UTC
The IMAP resource has a new maintainer, reassigning to him.
Comment 2 Christian Mollekopf 2013-11-24 19:37:25 UTC
Does this still apply for >= 4.11.3?
Comment 3 Andrew Crouthamel 2018-09-25 03:38:44 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-10-27 03:38:33 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!