Last updated on FEBRUARY 18, 2017
Applies to:Oracle Communications Messaging Server - Version 6.3 and later
Information in this document applies to any platform.
We have a Messaging Server install running and serving a local domain, myhost.example.edu and we are using Schema 1 with the Directory. We are in the process of migrating the mail domain to be hosted elsewhere, such that the MX record will then direct all mail @myhost.example.edu to a new exchanger and we will eventually retire the MS install.
After the switch over and MX record change we would like to continue to keep the MS MTA running and use it to relay mail as needed before we can retire it.
What configuration changes will be needed to make so the MTA will no longer consider itself serving the myhost.example.edu domain? Meaning IF the MTA receives mail destined for a user email@example.com will it still consider that user local and attempt to deliver it local, as opposed to doing a lookup and delivering the mail to the new MX?
The main concern is that after the MX record is changed and all mail for any @myhost.example.edu addresses is routed to the new system that authenticated users could, via an imap client, submit mail to the old system destined for users with an @myhost.example.edu address, in which case it would likely end up in a user's INBOX on the old system. What is the best way to avoid that?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms