Uploaded image for project: 'James Server'
  1. James Server
  2. JAMES-3102

Alias: using existing users as alias source

    XMLWordPrintableJSON

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.5.0
    • Component/s: RRT, webadmin
    • Labels:
      None

      Description

      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:

      curl -XPUT http://ip:port/address/aliases/user@domain.com/sources/alias@domain.com?bypassUserCheck
      

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              btellier Benoit Tellier
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: