Bug 323164 - Setting expire for a folder returns error NO Permission
Summary: Setting expire for a folder returns error NO Permission
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: 4.10
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Christian Mollekopf
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-04 13:44 UTC by Andreas Roth
Modified: 2017-01-07 22:19 UTC (History)
2 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 Andreas Roth 2013-08-04 13:44:58 UTC
I'm running a cyrus-imapd server (version 2.4.16) on Ubuntu 12.04 (without Kolab). I set up akonadi/KMail to access my imap account on the server. Getting/Reading mails works just fine.
When i try to the mail expiry properties for a folder i get the error 
Failed to write some annotations for 'myfolder' on the IMAP server. SetAnnotation failed, server replied: AXXXXXX NO Permission denied 
I get this error message exactly four times (with different AXXXX numbers).

As far is i know imap agent should set the annotation '/vendor/cmu/cyrus-imapd/expire' annotation (which is used by cyr_expire). 

The server error message suggests that the annotation is not understood or something is wrong with the SETANNOTATION command send to the server. For the folder in question i have the all permissions (imapacl in akonadi console: myname lrswipckxtdae %% myname lrswipcda).

Reproducible: Always

Steps to Reproduce:
1. set up cyrus-imapd mail server and account
2. try to adjust mail expiry properties for any folder

Actual Results:  
server returns no permission denied errors

Expected Results:  
aknonadi sets the /vendor/cmu/cyrus-imapd/expire annotation and server accepts it.
Comment 1 Kevin Ottens 2013-11-16 07:27:21 UTC
The IMAP resource has a new maintainer, reassigning to him.
Comment 2 Denis Kurz 2016-09-24 20:37:25 UTC
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 3 Denis Kurz 2017-01-07 22:19:16 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.