[ 
https://issues.apache.org/jira/browse/PROTOCOLS-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tellier Benoit updated PROTOCOLS-108:
-------------------------------------
    Issue Type: New Feature  (was: Bug)

> Add support for SETQUOTA, GETQUOTA and GETQUOTAROOT
> ---------------------------------------------------
>
>                 Key: PROTOCOLS-108
>                 URL: https://issues.apache.org/jira/browse/PROTOCOLS-108
>             Project: James Protocols
>          Issue Type: New Feature
>            Reporter: Tellier Benoit
>            Assignee: Eric Charles
>
> These commands are defined in RFC 2087.
> I implemented parsers, encoder, responses, and requests, with tests.
> What I need is to finish processors, and to do that I just need to know how 
> to handles rights. I asked these questions on the mailing lists :
> ```
> For GETQUOTAROOT, I made the choice that the user should have the
> read write on the mailbox.
>   
>     For GETQUOTA, I seems natural that the user should have the read
> permission on one of the mailbox belonging to the quota root. I bond
> quota root to be the user owning the mailbox...
>  How do I get all the mailboxes for a given user ? I gess I can
> achive this threw MailboxManager::search() but I have troubles
> understanding the way MailboxQuery works... I f you have any tips ...
>     We have an application ( OBM ) that uses the SETQUOTA command. We
> nowadays uses Cyrus, that allow an admin account to perform SETQUOTA
> operations. My question is :
>         Is there any ADMIN account in James ? Is their any way to
> achieve the same thing ? Of course SETQUOTA should be possible threw JMX
> ( I already implemented that ), but we realy want to do that in a
> standardized way using the SETQUOTA command.
> ```



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

Reply via email to