Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

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

Posted on 2014-07-30
1
Medium Priority
?
155 Views
Last Modified: 2014-07-31
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
0
Comment
Question by:Peter
1 Comment
 
LVL 3

Accepted Solution

by:
Keith Langmead earned 2000 total points
ID: 40231061
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

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article was originally published on Monitis Blog, you can check it here . Today it’s fairly well known that high-performing websites and applications bring in more visitors, higher SEO, and ultimately more sales. By the same token, downtime…
Among the most obnoxious of Exchange errors is error 1216 – Attached Database Mismatch error of the Jet Database Engine. When faced with this error, users may have to suffer from mailbox inaccessibility and in worst situations, permanent data loss.
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
Michael from AdRem Software outlines event notifications and Automatic Corrective Actions in network monitoring. Automatic Corrective Actions are scripts, which can automatically run upon discovery of a certain undesirable condition in your network.…
Suggested Courses
Course of the Month10 days, 16 hours left to enroll

572 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question