Hi folks,
We had Exchange 2010 and a hybrid deployment during our migration to Office 365. Now we have finished migrating all the mailboxes, public folders, etc. to Office 365 and I have removed the hybrid configuration and decommissioned the Exchange 2010 infrastructure. However, I have added one on-prem Exchange 2013 server for management tasks such as adding and removing email addresses, etc. as per the recommendations in this article: http://blogs.technet.com/b/exchange/archive/2012/12/05/decommissioning-your-exchange-2010-servers-in-a-hybrid-deployment.aspx. It has the mailbox and CAS roles installed. I had to add the mailbox role to get the EAC to run, but it hosts no mailboxes.
Up 'til now, I have used an IIS server to relay SMTP system messages to our Office 365 mailboxes (no mail to other domains), but this is not that reliable, and I would rather use the on-prem Exchange 2013 server to accomplish this task if I can.
I've created various types of send connectors to attempt this using *.contoso.com as the address space, and smarthosting to the address listed in our domain's MX record, but they are not working. I'm wondering since the server is part of our domain (contoso.com), whether it will route messages bound for that domain to a different host? I don't really see anything in the queues, so not sure where to begin troubleshooting.
I'm not sure if this can be done, and none of my searches are turning up anything on it; every other post advises using IIS.
Any help? Thanks,
ianc