Tickets :: Comment on [#10079] Cannot delete messages on RFC2086-only servers

* Your Email Address
* Spam protection	Enter the letters below: __ .__.._..__ . . / `[__] \| [__)\|_/ \__.\| \|_\|_\| \| \
Comment	>>> Not necessarily. Cyrus is still using 2086 ACLs if those were >>> generated (i.e. the mailbox created) with a Cyrus version that didn't >>> support 4314. ACLs are not automatically updated when updating Cyrus, >>> but only if the ACL is explicitely changed, using the newer Cyrus >>> version. >> >> Directly from RFC 4314: >> >> () Clients conforming to this document MUST ignore the virtual "d" >> and "c" rights in MYRIGHTS, ACL, and LISTRIGHTS responses. >> >> Thus, c and d rights need to be ignored. Not really sure how to work >> around this. > > So in your example: > > (1305381018,4323) S: MYRIGHTS INBOX.horde.cvs lrswipcda > > We need to treat this as: lrswipa > > Since this user is missing the 't' right: > > t - delete messages (set or clear \DELETED flag via STORE, set > \DELETED flag during APPEND/COPY) > > they don't have delete message access in that mailbox. And in this > case, we can't auto-detect if a server is returning RFC > 2086-compliant rights or RFC 4314 compliant-rights since, according > to your explanation, they are returning both (so we can't CAPABILITY > sniff for RIGHTS=).
Attachment
Watch this ticket