SOLVED

External SMTP flow for Hybrid environment

%3CLINGO-SUB%20id%3D%22lingo-sub-85242%22%20slang%3D%22en-US%22%3EExternal%20SMTP%20flow%20for%20Hybrid%20environment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-85242%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20running%20a%20hybrid%20environment%20with%20Office%20365.%20All%20mailboxes%20are%20in%20Exchange%20Online%20and%20I%20am%20trying%20to%20minimize%20my%20Exchange%202013%20footprint%20on-prem.%20My%20programs%2C%20printers%2C%20and%20devices%20point%20to%20a%20DNS%20record%20that%20goes%20to%20our%20Netscalers.%20The%20Netscaler%20sends%20email%20to%20the%20hybrid%20server%20(Exchange%202013%20CU12)%2C%20then%20up%20to%20365%2C%20via%20certificate.%3C%2FP%3E%3CP%3EWhen%20I%20test%20an%20email%20from%20one%20of%20my%20devices%2C%20it%20is%20successful%20if%20the%20email%20address%20is%20internal%20(same%20domain).%20But%20if%20the%20email%20is%20external%20I%20get%20the%20error%20message%20that%20the%20email%20address%20is%20invalid%2C%20and%20the%20email%20is%20not%20sent.%3C%2FP%3E%3CP%3EI%20have%20set%20the%20receive%20connector%20for%20the%20hybrid%20to%20'Anonymous%20Users'%20only.%20I%20have%20included%20the%20IP%20addresses%20of%20the%20netscaler.%3C%2FP%3E%3CP%3EIf%20I%20set%20the%20recieve%20connector%20to%20include%20the%20authentication%20option%20of%20TLS%2C%20then%20the%20external%20email%20will%20go%20through.%20The%20only%20problem%20is%20that%20the%20path%20is%20as%20followes%3A%20Device%20%26gt%3B%20Netscaler%20%26gt%3B%20hybrid%20server%20%26gt%3B%20other%20on-prem%20Exchange%20server%20%26gt%3B%20hybrid%20server%20%26gt%3B%20365.%3C%2FP%3E%3CP%3EI%20am%20trying%20to%20get%20rid%20of%20the%20'other%20on-prem%20Exchange%20server'.%20Any%20suggestions%20would%20be%20appreciated.%20Been%20working%20on%20this%20for%20a%20couple%20of%20weeks%2C%20and%20ready%20to%20get%20it%20off%20my%20plate.%3C%2FP%3E%3CP%3EThanks%2C%3CBR%20%2F%3EJason%20H%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-85242%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-85399%22%20slang%3D%22en-US%22%3ERe%3A%20External%20SMTP%20flow%20for%20Hybrid%20environment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-85399%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Nuno%20for%20your%20help.%20%26nbsp%3BThis%20might%20get%20me%20closer%20to%20our%20overall%20end%20goal%20of%20no%20exchange%20environment.%20%26nbsp%3BBut%20the%20following%20article%20got%20me%20going%20by%20changing%20up%20the%20receive%20connector%20a%20little%20bit.%20%26nbsp%3BNow%20both%20internal%20and%20external%20emails%20are%20sending%20out%20through%20the%20hybrid%20to%20365%20EOP.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22http%3A%2F%2Fwww.sunilchauhan.info%2F2016%2F05%2Fsetting-up-anonymous-relay-on-exchange.html%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fwww.sunilchauhan.info%2F2016%2F05%2Fsetting-up-anonymous-relay-on-exchange.html%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJason%20H%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-85343%22%20slang%3D%22en-US%22%3ERe%3A%20External%20SMTP%20flow%20for%20Hybrid%20environment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-85343%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Jason%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20can%20chose%20the%202%20options%2C%20it%20always%20depends%20what%20you%20need.%20For%20me%20I%20always%20prefer%20to%20keep%20hybrid%20because%20the%20management%2C%20but%20you%20can%20have%20your%20scanners%20pointed%20directly%20to%20your%20MX%20with%20the%20connector%20created%20like%20the%20article%20says.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20can%20keep%20the%20connetor%20for%20the%20hybrid%20and%20create%20a%20new%20one.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-85284%22%20slang%3D%22en-US%22%3ERe%3A%20External%20SMTP%20flow%20for%20Hybrid%20environment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-85284%22%20slang%3D%22en-US%22%3E%3CP%3ENuno%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20the%20fast%20response.%20%26nbsp%3BLet%20me%20see%20if%20I%20get%20this%20right%3A%20%26nbsp%3BSince%20my%20hybrid%20has%20a%20NAT%20to%20an%20external%20IP%20(example%3A%20%26nbsp%3B1.1.1.17)%2C%20and%20that%20IP%20is%20in%20my%20SPF%20record%2C%20and%20the%20receive%20connector%20in%20365%20has%20the%20cert%20which%20has%20the%20SAN%20that%20points%20to%20that%20IP%3A%20%26nbsp%3Ball%20I%20would%20need%20to%20do%20is%20point%20the%20Netscaler%20to%20our%20MX%20record%2C%20and%20it%20will%20go%20through%20the%20hybrid%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EQuestions%3A%3C%2FP%3E%3CP%3E1.%20Would%20I%20need%20to%20change%20the%20connector%20in%20365%20to%20accept%20by%20IP%20or%20does%20the%20cert%20work%3F%3C%2FP%3E%3CP%3E2.%20Can%20I%20NAT%20the%20netscaler%20out%2C%20and%20add%20the%20IP%20and%20be%20able%20to%20remove%20the%20hybrid%20from%20the%20equation%3F%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3EJason%20H%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-85254%22%20slang%3D%22en-US%22%3ERe%3A%20External%20SMTP%20flow%20for%20Hybrid%20environment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-85254%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Jason%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20think%20the%20problem%20could%20be%20that%20you%20are%20pointing%20to%20the%20connector%20directly.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20can%20create%20a%20receive%20connector%20on%20Office%20365%20that%20receives%20from%20your%20Public%20IP%20and%20then%20you%20can%20point%20your%20Netscaler%20to%20your%20MX%20Record%20that%20will%20connect%20to%20your%20connector.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESee%20option%202%20on%20this%20article%20-%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FHow-to-set-up-a-multifunction-device-or-application-to-send-email-using-Office-365-69f58e99-c550-4274-ad18-c805d654b4c4%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FHow-to-set-up-a-multifunction-device-or-application-to-send-email-using-Office-365-69f58e99-c550-4274-ad18-c805d654b4c4%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

I am running a hybrid environment with Office 365. All mailboxes are in Exchange Online and I am trying to minimize my Exchange 2013 footprint on-prem. My programs, printers, and devices point to a DNS record that goes to our Netscalers. The Netscaler sends email to the hybrid server (Exchange 2013 CU12), then up to 365, via certificate.

When I test an email from one of my devices, it is successful if the email address is internal (same domain). But if the email is external I get the error message that the email address is invalid, and the email is not sent.

I have set the receive connector for the hybrid to 'Anonymous Users' only. I have included the IP addresses of the netscaler.

If I set the recieve connector to include the authentication option of TLS, then the external email will go through. The only problem is that the path is as followes: Device > Netscaler > hybrid server > other on-prem Exchange server > hybrid server > 365.

I am trying to get rid of the 'other on-prem Exchange server'. Any suggestions would be appreciated. Been working on this for a couple of weeks, and ready to get it off my plate.

Thanks,
Jason H

4 Replies

Hi Jason,

 

I think the problem could be that you are pointing to the connector directly.

 

You can create a receive connector on Office 365 that receives from your Public IP and then you can point your Netscaler to your MX Record that will connect to your connector.

 

See option 2 on this article - https://support.office.com/en-us/article/How-to-set-up-a-multifunction-device-or-application-to-send...

Nuno,

 

Thanks for the fast response.  Let me see if I get this right:  Since my hybrid has a NAT to an external IP (example:  1.1.1.17), and that IP is in my SPF record, and the receive connector in 365 has the cert which has the SAN that points to that IP:  all I would need to do is point the Netscaler to our MX record, and it will go through the hybrid?

 

Questions:

1. Would I need to change the connector in 365 to accept by IP or does the cert work?

2. Can I NAT the netscaler out, and add the IP and be able to remove the hybrid from the equation?  

 

Thanks,

Jason H

best response confirmed by Jason Hopp (Occasional Contributor)
Solution

Hi Jason,

 

You can chose the 2 options, it always depends what you need. For me I always prefer to keep hybrid because the management, but you can have your scanners pointed directly to your MX with the connector created like the article says.

 

You can keep the connetor for the hybrid and create a new one.

Thanks Nuno for your help.  This might get me closer to our overall end goal of no exchange environment.  But the following article got me going by changing up the receive connector a little bit.  Now both internal and external emails are sending out through the hybrid to 365 EOP.

 

http://www.sunilchauhan.info/2016/05/setting-up-anonymous-relay-on-exchange.html

 

Jason H