jnoble123
asked on
Company splits into two, old Windows domain still in use including active directory in both companies, mail won't route
At one time we were one big company that we will call OriginalCompany for simplicity. Later the OriginalCompany split into two companies as part of a sell off resulting in NewCompany and OiginalCompany.
When the split occurred both OriginalCompany and NewCompany kept the same Windows Domain names internally, along with the Active Directory even though the two parts are no longer physically connected in anyway.
Our external internet domain has changed from OriginalCompany.com to NewCompany.com and email is working in all cases but one. When we try to send mail to someone at OriginalCompany.com it never seems to route past the exchange 2003 server. I believe that there is likely a configuration that needs to be changed.
Any ideas?
When the split occurred both OriginalCompany and NewCompany kept the same Windows Domain names internally, along with the Active Directory even though the two parts are no longer physically connected in anyway.
Our external internet domain has changed from OriginalCompany.com to NewCompany.com and email is working in all cases but one. When we try to send mail to someone at OriginalCompany.com it never seems to route past the exchange 2003 server. I believe that there is likely a configuration that needs to be changed.
Any ideas?
ASKER
Not using that email for external email now using NewCompany.com instead of OriginalCompany.com.
Not sure about recipient policy. I will check.
~Jamie N
Not sure about recipient policy. I will check.
~Jamie N
ASKER
We have two recipient policies.
The highest priority one has the correct SMTP info. The lowest priority one (also the default) has the incorrect internet SMTP domain info. Unfortunately I can't seem to delete or modify the default policy. Any suggestions?
~Jamie N
The highest priority one has the correct SMTP info. The lowest priority one (also the default) has the incorrect internet SMTP domain info. Unfortunately I can't seem to delete or modify the default policy. Any suggestions?
~Jamie N
You cannot delete the default recipient policy.
I wouldn't suggest removing the domain from it either - if that domain has been used for the active directory that will upset things.
Do any users in the other company appear in your GAL for any reason whatsoever?
Simon.
I wouldn't suggest removing the domain from it either - if that domain has been used for the active directory that will upset things.
Do any users in the other company appear in your GAL for any reason whatsoever?
Simon.
ASKER
I didn't think deleting it would be possible but I was hopeful if it wasn't disruptive.
Yes, unfortunately we do have a few particular contacts in the old company that we do need to communicate with. This is ultimately what's driving the issue.
I wonder if I could do something like an alias at the unix email gateway to retranslate a fake address into the proper address after the message has left exchange?
ie.
email ==> jamie@tempoldcompany.com
alias conversion == jamie@tempoldcompany.com ==> jamie@originalcompany.com
That would get the email out anyway. Thoughts?
~Jamie N
Yes, unfortunately we do have a few particular contacts in the old company that we do need to communicate with. This is ultimately what's driving the issue.
I wonder if I could do something like an alias at the unix email gateway to retranslate a fake address into the proper address after the message has left exchange?
ie.
email ==> jamie@tempoldcompany.com
alias conversion == jamie@tempoldcompany.com ==> jamie@originalcompany.com
That would get the email out anyway. Thoughts?
~Jamie N
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Are you still using that domain for external email?
Simon.