[Tickets #10079] Re: Cannot delete messages

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/10079
------------------------------------------------------------------------------
  Ticket             | 10079
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Cannot delete messages
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Assigned
  Priority           | 3. High
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2011-05-16 17:20) wrote:

>> 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=).