Last updated on SEPTEMBER 20, 2017
Applies to:Oracle Communications Messaging Server - Version 8.0.0 and later
Information in this document applies to any platform.
Oracle Communications Messaging Server 22.214.171.124.20170825 64bit (built Aug 25 2017)
libimta.so 126.96.36.199.20170825 64bit (built 17:38:25, Aug 25 2017)
Using /opt/sun/comms/messaging64/config/config.xml (compiled)
NSS Library Version: 3.32
SunOS mshost 5.10 Generic_150400-49 sun4v sparc sun4v
We are going to bring a new group of users into our corporate email service. They must retain their @filecreator.com email addresses. They are currently running on their own mail service since before the acquisition.
While trying to decide the best strategy to define this in LDAP, so that users who have been switched over to the corporate email service will get delivered "locally" and users who are still on the old systems will be routed to the old systems, we noticed it is already defined in our LDAP as this entry:
dn: dc=filecreator, dc=com, o=internet
description: DC node for filecreator.com
mailRoutingHosts: ns2.filecreator.com <<<<<<<<<<<<<<<<<<
Note that there is NOTHING defined under dc=filecreator,dc=com,o=internet, so it can never find any users/groups there.
We do NOT have route_to_routing_host set. The default is 0.
instance.base.hostname = mshost.abc.com
Question: It is working in that the presence of the dc=filecreator,dc=com,o=internet object is not causing any problem with routing to that domain. Why is this working? From the imsimta test -rewrite output, why was it NOT trying to lookup users in that domain and then failing? Is the lack of any users/groups objects under the container indicated by inetDomainBaseDN enough to cause it to not treat the above LDAP entry as a valid domain?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms