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

Tellier Benoit commented on JAMES-2637:
---------------------------------------

https://github.com/linagora/james-project/pull/2099 is merged

> Webadmin CRUD for RRT aliases
> -----------------------------
>
>                 Key: JAMES-2637
>                 URL: https://issues.apache.org/jira/browse/JAMES-2637
>             Project: James Server
>          Issue Type: New Feature
>          Components: RRT, webadmin
>            Reporter: Tellier Benoit
>            Priority: Major
>
> We should be able to update aliases using the webadmin protocol
> Here is the proposed API:
> {code:java}
> PUT /address/aliases/[email protected]/sources/[email protected]
> Adds a `bob-alias` alias pointing to `[email protected]` main mail address
> 204
> 400 if the alias source (`[email protected]`) is contained in 
> UsersRepository
> 400 if source or destination domain is not handled by James
> No content
> {code}
> (implement PUT in a separate pull request as this is an emergency?)
> {code:java}
> GET /address/aliases
> Returns the mailAddresses having aliases configured.
> 200
> ["[email protected]", "[email protected]"]
> {code}
> {code:java}
> DELETE /address/aliases/[email protected]/sources/[email protected]
> Deletes the `bob-alias` alias pointing to `[email protected]` main mail address
> 204
> No content
> {code}
> {code:java}
> GET /address/aliases/[email protected]
> Will return all the aliases pointing to [email protected] main mail address
> 200
> [
>     {"source":"[email protected]"},
>     ...
> ]
> {code}
> Create a `AliasRoutes` class in `/server/protocols/webadmin/webadmin-data` 
> and the corresponding tests using the MemoryRecipientRewriteTable.
> Have a look to `ForwardsRoutes` for guidance



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to