[ 
https://issues.apache.org/jira/browse/IMAP-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205302#comment-13205302
 ] 

Jochen Gazda commented on IMAP-351:
-----------------------------------

Just to sum up the state of the tasks mentioned in the original post:

> (1) I have put some FIXMEs and TODOs in the patch where somebody 
> experienced should please have a look.

See IMAP-354, IMAP-355, IMAP-356, MAILBOX-156, MAILBOX-157 and MAILBOX-158

> (2) ACL getter and setter stubs should be filled in Mailbox 
> implementations. New tests should be added for those getters and 
> setters.

See MAILBOX-161, MAILBOX-162, MAILBOX-163 and MAILBOX-158

> (3) Mapping of ACL Rights to READ-WRITE and READ-ONLY Response Codes,
> see RFC 4314 section 5.2. 

See MAILBOX-160

> (4) Enforce rights required to perform different IMAP4rev1 Commands in 
> IMAP processors, see RFC 4314 section 4. Write tests. 

See IMAP-358

> (5) MailboxACLUpdated event should be fired and litstened to.

See MAILBOX-164

(6) A new one: IMAP-359 Implement missing ACL commands SETACL, LISTRIGHTS and 
MYRIGHTS

                
> ACL Support
> -----------
>
>                 Key: IMAP-351
>                 URL: https://issues.apache.org/jira/browse/IMAP-351
>             Project: JAMES Imap
>          Issue Type: New Feature
>          Components: JCR Mailbox, JPA Mailbox, Mailbox, Maildir Mailbox, 
> Parser, Processor, Protocol
>    Affects Versions: 0.3
>            Reporter: Jochen Gazda
>              Labels: ACL, IMAP
>             Fix For: 0.3
>
>         Attachments: IMAP-GETACL.txt, ImapGetACLTest.java
>
>   Original Estimate: 672h
>  Remaining Estimate: 672h
>
> Support for RFC 4314 IMAP4 Access Control List (ACL) Extension

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to