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 "Dat Pham (JIRA)" <se...@james.apache.org> on 2018/11/06 02:31:00 UTC
[jira] [Updated] (JAMES-2585) As an admin, I can manage sieve
scripts
[ https://issues.apache.org/jira/browse/JAMES-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dat Pham updated JAMES-2585:
----------------------------
Description:
See https://ci.linagora.com/linagora/lgs/openpaas/james/issues/833 for the context of this task
The goal is to allow the admin to manage user Sieve scripts.
This should allow webadmin to leverage the feature of the AddActiveSieveScript command.
Story:
{code:java}
As an admin, using the WebAdmin protocol...
... Upload a new Sieve Script
{code}
API proposal
404 if the user does not exist
{code:java}
POST /sieve/bob@domain.tld/scripts/script_name.sieve
'
require "fileinto";
require "body";
if body :raw :contains "invalid" {
fileinto "INBOX.select";
} else {
fileinto "INBOX.not.selected";
}
'
{code}
will create the Sieve script
You will add a activate query parameter for automatically activating the script.
{code:java}
POST /sieve/bob@domain.tld/scripts/script_name.sieve.activate=true
'
require "fileinto";
require "body";
if body :raw :contains "invalid" {
fileinto "INBOX.select";
} else {
fileinto "INBOX.not.selected";
}
'
{code}
was:
See https://ci.linagora.com/linagora/lgs/openpaas/james/issues/833 for the context of this task
The goal is to allow the admin to manage user Sieve scripts.
This should allow webadmin to leverage the feature of the AddActiveSieveScript command.
Story:
{code:java}
As an admin, using the WebAdmin protocol...
... Upload a new Sieve Script
{code}
API proposal
404 if the user does not exist
{code:java}
POST /sieve/bob@domain.tld/scripts/script_name.sieve
'
require "fileinto";
require "body";
if body :raw :contains "invalid" {
fileinto "INBOX.select";
} else {
fileinto "INBOX.not.selected";
}
'
{code}
will create the Sieve script
You will add a activate query parameter for automatically activating the script.
POST /sieve/bob@domain.tld/scripts/script_name.sieve.activate=true
'
require "fileinto";
require "body";
if body :raw :contains "invalid" {
fileinto "INBOX.select";
} else {
fileinto "INBOX.not.selected";
}
'
> As an admin, I can manage sieve scripts
> ---------------------------------------
>
> Key: JAMES-2585
> URL: https://issues.apache.org/jira/browse/JAMES-2585
> Project: James Server
> Issue Type: Improvement
> Reporter: Dat Pham
> Priority: Major
>
> See https://ci.linagora.com/linagora/lgs/openpaas/james/issues/833 for the context of this task
> The goal is to allow the admin to manage user Sieve scripts.
> This should allow webadmin to leverage the feature of the AddActiveSieveScript command.
> Story:
> {code:java}
> As an admin, using the WebAdmin protocol...
> ... Upload a new Sieve Script
> {code}
> API proposal
> 404 if the user does not exist
> {code:java}
> POST /sieve/bob@domain.tld/scripts/script_name.sieve
> '
> require "fileinto";
> require "body";
> if body :raw :contains "invalid" {
> fileinto "INBOX.select";
> } else {
> fileinto "INBOX.not.selected";
> }
> '
> {code}
> will create the Sieve script
> You will add a activate query parameter for automatically activating the script.
> {code:java}
> POST /sieve/bob@domain.tld/scripts/script_name.sieve.activate=true
> '
> require "fileinto";
> require "body";
> if body :raw :contains "invalid" {
> fileinto "INBOX.select";
> } else {
> fileinto "INBOX.not.selected";
> }
> '
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org