Benoit Tellier created JAMES-3102:
-------------------------------------
Summary: Alias: using existing users as alias source
Key: JAMES-3102
URL: https://issues.apache.org/jira/browse/JAMES-3102
Project: James Server
Issue Type: New Feature
Components: RRT, webadmin
Reporter: Benoit Tellier
Fix For: 3.5.0
We are using LDAP repository.
User A had been changing name (to user B) and both entries exist in the LDAP.
We cannot delete user A from the LDAP
Thus we want to be able to 'force' the alias insertion despite the rule that a
user can't be used as an alias source.
Traffic of user A will effectively be redirected to user B. Moreover User B
will still be able to send mails using user A identify (not possible with
forwards).
The proposal is to introduce a new query parameter allowing to bypass the
check, while keeping the behaviour untouched otherwise.
Example:
{code:java}
curl -XPUT
http://ip:port/address/aliases/[email protected]/sources/[email protected]?bypassUserCheck
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
