You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Tellier Benoit (JIRA)" <se...@james.apache.org> on 2017/09/22 07:04:00 UTC
[jira] [Updated] (JAMES-2151) Administer Sieve quotas via CLI
[ https://issues.apache.org/jira/browse/JAMES-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tellier Benoit updated JAMES-2151:
----------------------------------
Description:
James allows users to store Sieve scripts. As defined in ManageSieve RFC such storage should be limited by quotas. Hence, James allow administration of such quotas via the Command Line Client. But miss this administration aspect through *webadmin*.
In *webadmin-data* project, crete a *SieveQuota* route class directly calling *SieveRepository* to create, read and delete such quotas. Globally, and per user. You will write relevant unit tests.
You can have a look to the existing *GlobalQuotaRoutes* and related tests in *GlobalQuotaRoutesTest*.
Here is the proposed API:
{code:java}
GET /sieve/quota
150000
(Expressed in bytes)
PUT /sieve/quota
160000
DELETE /sieve/quota
GET /sieve/quota/:user
150000
(Expressed in bytes)
PUT /sieve/quota/:user
160000
DELETE /sieve/quota/:user
{code}
Don't hesitate to ask for help on the *Gitter* chat.
was:
James allows users to store Sieve scripts. As defined in ManageSieve RFC such storage should be limited by quotas. Hence, James allow administration of such quotas via the Command Line Client. But miss this administration aspect through *webadmin*.
In *webadmin-data* project, crete a *SieveQuota* route class directly calling *SieveRepository* to create, read and delete such quotas. Globally, and per user. You will write relevant unit tests.
You can have a look to the existing *GlobalQuotaRoutes* and related tests in *GlobalQuotaRoutesTest*.
Here is the proposed API:
{code:java}
GET /sieve/quota
{code}
> Administer Sieve quotas via CLI
> -------------------------------
>
> Key: JAMES-2151
> URL: https://issues.apache.org/jira/browse/JAMES-2151
> Project: James Server
> Issue Type: New Feature
> Components: webadmin
> Affects Versions: master
> Reporter: Tellier Benoit
> Labels: feature, newbie
>
> James allows users to store Sieve scripts. As defined in ManageSieve RFC such storage should be limited by quotas. Hence, James allow administration of such quotas via the Command Line Client. But miss this administration aspect through *webadmin*.
> In *webadmin-data* project, crete a *SieveQuota* route class directly calling *SieveRepository* to create, read and delete such quotas. Globally, and per user. You will write relevant unit tests.
> You can have a look to the existing *GlobalQuotaRoutes* and related tests in *GlobalQuotaRoutesTest*.
> Here is the proposed API:
> {code:java}
> GET /sieve/quota
> 150000
> (Expressed in bytes)
> PUT /sieve/quota
> 160000
> DELETE /sieve/quota
> GET /sieve/quota/:user
> 150000
> (Expressed in bytes)
> PUT /sieve/quota/:user
> 160000
> DELETE /sieve/quota/:user
> {code}
> Don't hesitate to ask for help on the *Gitter* chat.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org