How To Use a Smart Host on a Domain With an External Hostname and Avoid tcp_local's Daemon Option?
(Doc ID 2058307.1)
Last updated on MARCH 12, 2021
Applies to:Oracle Communications Messaging Server - Version 7.0.0 and later
Information in this document applies to any platform.
Considering the following situation:
- an Oracle Messaging Server serves a local email domain, but
- there is a second mail server, which serves another piece of the same email domain.
On the Oracle Messaging Server, there is a daemon defined on the tcp_local channel which points to an anti-virus MX. The mail also comes in through this MX.
The second mail server is running non-Oracle software, has an external host name (unrelated to the mail domain), and has users which are NOT defined in the LDAP server (as used by the primary Messaging Server).
The following behavior is desired:
- mail coming in through our MX is delivered to our primary messaging server.
- if the user is defined on this primary messaging server, mail is delivered in the user's mailbox,
- else, if the user is not defined in LDAP, the mail should go to the second non-Oracle mail server.
1) Mail coming through our MX/antispam system are delivered to our Oracle messaging server
2) If the user is local, mail is delivered
3) Else (users not local/not in the local LDAP), the mail is relaying internally to the second mail sever (NO LDAP/Not Oracle), which will handle it.
How can we do this?
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