#[non_exhaustive]pub struct MailboxRights {
pub may_read_items: bool,
pub may_add_items: bool,
pub may_remove_items: bool,
pub may_set_seen: bool,
pub may_set_keywords: bool,
pub may_create_child: bool,
pub may_rename: bool,
pub may_delete: bool,
pub may_submit: bool,
pub may_set_metadata: Option<bool>,
pub extra: Map<String, Value>,
}Expand description
Access control rights the authenticated user holds for a Mailbox (RFC 8621 §2).
Backwards compatible with IMAP ACLs (RFC 4314).
Default produces all-false (no access), which is the most restrictive valid value
and a safe starting point when constructing rights in tests or server code.
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.may_read_items: boolUser may use this Mailbox in Email/query filters and read its emails.
may_add_items: boolUser may add mail to this Mailbox.
may_remove_items: boolUser may remove mail from this Mailbox.
may_set_seen: boolUser may add or remove the $seen keyword on emails in this Mailbox.
may_set_keywords: boolUser may add or remove keywords other than $seen on emails.
may_create_child: boolUser may create a child Mailbox under this one.
may_rename: boolUser may rename this Mailbox or move it under another parent.
may_delete: boolUser may delete this Mailbox.
may_submit: boolMessages may be submitted directly to this Mailbox.
may_set_metadata: Option<bool>User may modify the shared metadata of this Mailbox and of the Emails
in it (draft-ietf-jmap-metadata-04 §4.1; IMAP ACL “n” right, RFC 5257).
None when the server omits it: the right is present only when the
metadata capability lists this type or a type it contains (§4.1).
extra: Map<String, Value>Catch-all for vendor / site / private extension fields not covered by the typed fields above. Preserves unknown fields across deserialize/serialize round-trip per workspace extras-preservation policy (see workspace AGENTS.md).