How to Achieve Multiple Domain Aliasing by Using Rewrite Rules
(Doc ID 2524023.1)
Last updated on NOVEMBER 08, 2019
Applies to:Oracle Communications Messaging Server - Version 8.0.1 and later
Information in this document applies to any platform.
We are trying to move all users from multiple domains: 'domain1.com', 'domain2.com' and 'domain3.com' to a new domain: 'alias.com' over time.
At any point in time, mail must be able to be delivered to the existing domains and the target domain (alias.com), regardless of when a user is migrated. Also note that the left hand side of the address is guaranteed unique across multiple domains.
Typically, we would tackle this by populating MailEquivalentAddress of firstname.lastname@example.org to each user to ensure delivery of mail to the new domain. When each of the addresses are migrated to alias.com, we would add the "old" domain1/domain2/domain3.com to MailEquivalentAddress and call it a day. We actually plan to perform the second step when the user is migrated by leveraging the mailequivalent address. However, some outside reason has prohibited us from performing the first part, which is to populate all existing users with alias.com to the MailEquivalentAddress attribute and this is why we want to solve this first part via a re-write rule.
We have actually come up with a way to tackle this but we do not like the fact that we are almost doubling the LDAP lookups as we migrate more users and we wonder if there is a better way. The rules we came up with are:
We'd rather place that new rewrite rule after the original $* rule but it won't work because LDAP processing terminates rewrite processing when a user is not found in the search. How can we optimize this?
The end state is to move all users from the different domains: domain1.com, domain2.com, domain3.com to alias.com over time.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document