Forum Discussion
How to use on-premis smtp relay name with office365
My pleasure!
If you want some redundancy, what I normally suggest is to spin up a second Exchange 2016 server and add the same connector. If you needed to flip over to it, you could change your internal smtp dns entry to point to the IP of the backup.
Ah I get you. When you create your Exchange 2016 server, you will need to create a new receive connector in the Exchange Admin Center. You will have a similar one in Exchange 2010 for SMTP relay.
Once it's set, you need to switch one of your devices / software over to it to test, and then slowly change everything over to it.
Hi Peter,
Thanks, But no receive connector with those IP's or SMTP name? I think smtp.mydomain.com is not relaying via Exchange. No edge subscription in exchange 2010? I'm confused.
As
PeterRising Hi Peter,
Are you recommend to set up this Exchange 2016 server in on-premise or Cloud ( AWS)
if it is in AWS, can I use the free Exchange License?
As
My pleasure!
If you want some redundancy, what I normally suggest is to spin up a second Exchange 2016 server and add the same connector. If you needed to flip over to it, you could change your internal smtp dns entry to point to the IP of the backup.
HI Peter,
Thank you so much for your information. Yes, I can do that. One more question.
How do we set up redundancy for SMTP Relay? We have one Exchange 2016 Server and Windows AD servers in Azure. So if this server goes down, how we handle the notification emails from our devices and applications?
I think allowing on-premise SMTP traffic to AWS is not a good idea.
As
Ah OK, you would need to either change your internal DNS record for your SMTP name to be the IP address of the Exchange 2016 server when you were ready. Alternatively, you could switch the IP addresses and give the new Exchange 2016 server the same IP as the current Exchange 2010 SMTP relay server.