Relevant Products: Email Alias Manager for Exchange
Microsoft Outlook is not populated with alias addresses, and users cannot send messages from an alias address using the subject line trigger 'sendas:firstname.lastname@example.org.
Your setup is such that proxy addresses are only populated in Active Directory on a different domain (or subdomain) to the one which the user is logged in.
The Email Alias Manager Agent uses LDAP queries to verify a users’ available email aliases.
When an LDAP search is performed against a domain, the search considers all trusted domains and subdomains to be separate entities. This means that it does not recursively search all sub-domains from the root domain - each domain must be searched independently.
As such, the Email Alias Manager Agent can only search one domain or subdomain. So, if Email Alias Manager is searching an incorrect domain, the aliases will not be populated in Microsoft Outlook.
You can specify the domain (or sub domain) where Active Directory is populated with proxy addresses in the Windows Registry. This should be set on each machine which has the Email Alias Manager Outlook add-in installed.
If you are not familiar with the Windows registry, you may wish to read about it before attempting any changes.
- Click Start and then Run.
- Enter regedit and click OK to open the Registry Editor.
- Expand the tree in the left-hand pane and navigate to the path below:
- In the right-hand pane, right-click and select new > string value:
- Name the string value: LDAPRootString.
- Double-click the value to edit it.
- Enter the LDAP string for the domain where Active Directory is populated with proxy addresses. For example: LDAP://DC=Child,DC=Domain,DC=local
- Click OK and the change should take effect immediately.