IMAP Access Rights Reference¶
Stands for lookup.
The ACE subject can lookup this folder, and see that the folder exists, meaning the folder will appear in a LIST “” “*”.
Folders to which the ACE subject has no lookup rights may still be subscribed to. The lookup right is only required if Cyrus IMAP has been configured with the allowallsubscribe setting to false (0).
In Cyrus IMAP 2.5, this setting defaults to false (0).
In a Cyrus IMAP Murder, this setting is typically set to true (1).
The l can be assigned to a folder, without the l right having been given out for the parent folder. Cyrus IMAP will pretend the parent folder does not exist;
RFC 4314, section 4., page 13, states the following example:
Note that if the user has the l right to a mailbox
A/B, but not to its parent mailbox
A, the LIST command should behave as if the mailbox
Adoesn’t exist, for example:C: A777 LIST "" * S: * LIST (NoInferiors) "/" "A/B" S: * LIST () "/" "C" S: * LIST (NoInferiors) "/" "C/D" S: A777 OK LIST completed
Stands for read.
The ACE subject can read the contents of this folder, meaning that the ACE subject is allowed to SELECT or EXAMINE the folder, query its STATUS, FETCH data, SEARCH the contents, and COPY contents from the folder.
The r right also allows the user to GETMETADATA when used in conjunction with the l right, as defined in RFC 5464.
Stands for seen.
The ACE subject is permitted to maintain the ACE subject’s seen state for this folder, or the shared seen state in case the
/vendor/cmu/cyrus-imapd/sharedseenhas been set to true. Additionally, the Recent flags are preserved for the ACE subject.
Stands for write.
The ACE subject is permitted to write to the folder, actually meaning the ACE subject is permitted to maintain flags and keywords other then Seen and Deleted, which are controlled using the s**and **t rights respectively.
The w right also allows the user to SETMETADATA when used in conjunction with the l and r rights, as defined in RFC 5464.
IMAP clients may expect to be able to set flags other then Seen and Deleted and attempt to set those flags immediately along with a “Mark as read” action, without the ACE subject actually being permitted to set some of those flags through the w right.
RFC 4314, section 4., page 15, states that the server SHOULD NOT fail, as the tagged NO response is not handled very will by deployed clients. In order to comply, we have Bug #3488, as Cyrus IMAP currently does seem to issue a tagged NO response.
Stands for insert.
The ACE subject is permitted to insert content into a folder, meaning the ACE subject may COPY messages with this folder as the target folder, and may APPEND messages to this folder.
Stands for post.
The post right currently is exclusive to Cyrus IMAP, and allows the ACE subject to send email to the submission address for the mailbox.
This right differs from the i right in that the delivery system inserts trace information into submitted messages.
Example implementations using the p right include shared folders to which specific recipient addresses are delivered through LMTP pre- authorized as the postuser, which must then also have the p right on the target folder.
Stands for create.
The create right is a right introduced with RFC 2086 (IMAP4 ACL extension), indicating the ACE subject’s right to create new sub-folders in the parent folder on which this right has been assigned, but also to delete the same folder.
Since RFC 4314, the c right has been replaced with the k right to CREATE folders with, the x right to DELETE folders with.
The c right should no longer be used
Even though Cyrus IMAP is backwards compatible when it comes to the c right, which it implements as implying as the k right, implementations should not count on the c right backwards compability to be around forever, and to fully implement the legacy c right, use kx.
The ACE subject has the right to CREATE a new folder if the k exists on the parent folder of the folder created.
The rights required for a RENAME to be successful could be illustrated by describing a RENAME as a CREATE of the new folder, not exactly followed by a COPY on the old folder’s contents, but more like a move like on a filesystem, and finally a DELETE on the old folder.
As such, the k is the right required on the parent folder of the target folder, and the x right on the source folder. To further illustrate;
Suppose the ACE subject has the k right on folder “C/”, and the x right on folder “A/B”, then a RENAME A/B C/B would succeed.
Stands for administer.
The ACE subject is allowed to administer the folder, meaning the ACE subject is allowed to perform administrative operations on the folder. The a right is needed to successfully execute SETACL, DELETEACL (short for SETACL “”) and to execute GETACL or LISTRIGHTS.
IMAP clients may issue a GETACL in order to obtain the ACE subject’s rights on the folder, where they should be using MYRIGHTS, as GETACL or LISTRIGHTS return the full Access Control List, including other ACE subject’s identifiers.
Unless the ACE subject has the a right on a folder, issuing a GETACL or LISTRIGHTS will cause Cyrus IMAP to send a tagged “NO: Permission denied” response if the ACE subject has the l (lookup) right on the folder, and a “NO: No Such Mailbox” response otherwise, as per section 8. of RFC 2086 and section 6. of RFC 4314 – both conveniently called “Security Considerations”.
Use this to indicate the ACE subject has the right to delete the mailbox, as opposed to the c or d rights.
The ACE subject is allowed to delete messages from this folder, meaning that the ACE subject is allowed to flag messages as deleted.
In IMAP, messages are only actually deleted in a way that at least makes them invisible to the folder’s users need to be expunged. For the corresponding EXPUNGE however, the x right is required.
The ACE subject is allowed to annotate individual messages in this folder, in compliance with RFC 5257.
Please note that the ACE subject must also have the r right, or the subject won’t know which messages are available to annotate, however the r right is not implied (nor is the l right).
Stands for expunge.
The ACE subject is allowed to expunge messages in this folder, meaning the ACE subject has the right to remove all messages that have been flagged as deleted from all visibility.
In IMAP, expunging messages only applies to messages flagged as deleted. For the ACE subject to be able to flag messages as deleted however, the t right is required.
We say “remove from all visibility”, because the implementation of expunging messages in Cyrus IMAP is ACE subject to the expunge_mode in /etc/imapd.conf, which when set to delayed only causes the reference to the expunged messages to be deleted from the folder index database – effectively removing the expunged message(s) from all visibility, while they remain in place on the Cyrus IMAP server filesystem.
IMAP clients may expect to be able to EXPUNGE a folder regardless of the availability of this right.
Stands for delete.
This is the legacy, RFC 2086 access control right for the delete right. In versions of Cyrus IMAP implementing only this right, ACE subjects were allowed to flag messages as deleted and expunge folders.
The delete right has been split in to three separate rights, t (flag messages as deleted), e (expunge folder) and k (delete folder).
The deleteright setting in /etc/imapd.conf controls the RFC 2086 right which controls whether or not the ACE subject may delete a folder. However, this setting (as the original specification for the delete right was considered ambiguous) is ignored, and if it is set to c, is automatically converted to the x right.
The d right should no longer be used
Even though Cyrus IMAP is backwards compatible when it comes to the d right, which it implements as implying as the e and t rights, implementations should not count on the d right backwards compability to be around forever, instead use te rights.