[ https://issues.apache.org/jira/browse/JAMES-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benoit Tellier closed JAMES-3102. --------------------------------- Resolution: Fixed A misconfiguration caused the initial issue; this hach is no longer necessary > 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 > Priority: Major > Fix For: 3.5.0 > > > User A had been changing name (to user B) and both entries exist in the LDAP. > We want User B to send and receive mails from UserA address. > We are using LDAP repository. We cannot delete user A from the LDAP. We can > not create the alias as user A exists. > 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/u...@domain.com/sources/al...@domain.com?bypassUserCheck > {code} -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org