Help required please - in-house Exchange to Hosted - routing

Hi,

I am posting here for some advice please.

We have just migrated a customer's in-house SBS Exchange 2007 to a cloud-based Exchange solution (OneNet) but have had to keep one email domain in-house for now (don't ask).

How can I configure their Exchange server to send email to the newly created external OneNet mailboxes from that one in-house email domain? At the moment it appears to just want to route internally (to the old, in-house mailboxes) as it has always done in the past.

I'm thinking something via Exchange Console -> Hub Transport -> Organisation -> Send Connectors - SMTP?

Thanks,
Peter
PeterAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Keith LangmeadCommented:
If the in-house Exchange server no longer has references to the domains that have been moved to the external server, then Exchange should route all email (including those domains you've migrated) externally, and through that to the new cloud provider. If that's not happening then I'd expect your issue is that Exchange still thinks that it is responsible for the domain.

First thing to check, go into Organization Configuration > Hub Transport > Accepted Domains, and check that those migrated domains aren't still listed as Authoritative (or Internal Relay). If they are then depending on your setup you can either simply remove them from here, or if there are still any references to the domain locally (that you need to keep) then change them to External Relay, which will then forward any mail destined for an address not held locally out via the internet.

If your server is unable to lookup the migrated domains, and resolve them to the new hosting in the same way it would do for any other domain, then you'd want to add a Send Connector. Most likely causes would be that you've had to keep a reference to them in Accepted Domains, or the local DNS still has the domains listed locally with records pointing elsewhere. If that's the case then you could add a send connector for them within Hub Transport, and from there route all mail destined for one of those domains through the relevant smart host, eg the inbound server address of your cloud based Exchange server.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Server Software

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.