Exchange 2019 multi-tenant - mail flow - sending between tenants?

%3CLINGO-SUB%20id%3D%22lingo-sub-2280092%22%20slang%3D%22en-US%22%3EExchange%202019%20multi-tenant%20-%20mail%20flow%20-%20sending%20between%20tenants%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2280092%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20built%20a%20Exchange%202019%20Multi-tenant%20server%20using%20the%26nbsp%3Brecommendations%26nbsp%3Bmade%20in%20the%20document%20below%20and%20step-by-steps%20provided%20for%20Exchange%202019%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D36790%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D36790%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20sending%20e-mails%20between%20clients%20(tenants)%20who%20are%20hosted%20on%20the%20multi-tenant%20Exchange%2C%20mail%20is%20sent%20directly%20within%20Exchange%20as%20Exchange%20knows%20who%20everyone%20is.%3C%2FP%3E%3CP%3EWe%20need%20Exchange%20to%20always%20send%20out%20mail%20via%20SMTP%20if%20the%20receiving%20domain%20is%20not%20their%20own%3CBR%20%2F%3EEg%3A%26nbsp%3Bsmith%40abc.om%20to%20jones%40abc.com%20%E2%80%93%20can%20be%20delivered%20internally%20by%20Exchange%3CBR%20%2F%3Ebut%3CBR%20%2F%3Esmith%40abc.om%20to%20bob%40xyz.com%20%E2%80%93%20must%20be%20sent%20via%20SMTP%20%E2%80%93%20out%20to%20the%20internet%20and%20back%20again.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20way%20to%20force%20SMTP%20outgoing%20e-mail%20to%20use%20MX%20records%20and%20not%20route%20internally%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20problem%20here%20is%20%3A%3CBR%20%2F%3EA)%20When%20setting%20up%20or%20migrating%20a%20new%20client%2C%20once%20the%20domain%20for%20that%20client%20is%20in%20Exchange%20and%20the%20user%20is%20set%20up%2C%20any%20mail%20we%20try%20to%20send%20to%20that%20client%20will%20be%20delivered%20Internally%20even%20though%20we%20really%20haven%E2%80%99t%20activated%20the%20client.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks.%3C%2FP%3E%3CP%3ESean%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2280092%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%202019%20multi-tenant%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Senior Member

We have built a Exchange 2019 Multi-tenant server using the recommendations made in the document below and step-by-steps provided for Exchange 2019:
https://www.microsoft.com/en-us/download/details.aspx?id=36790

 

When sending e-mails between clients (tenants) who are hosted on the multi-tenant Exchange, mail is sent directly within Exchange as Exchange knows who everyone is.

We need Exchange to always send out mail via SMTP if the receiving domain is not their own
Eg: smith@abc.om to jones@abc.com – can be delivered internally by Exchange
but
smith@abc.om to bob@xyz.com – must be sent via SMTP – out to the internet and back again.

 

Is there a way to force SMTP outgoing e-mail to use MX records and not route internally?

 

The problem here is :
A) When setting up or migrating a new client, once the domain for that client is in Exchange and the user is set up, any mail we try to send to that client will be delivered Internally even though we really haven’t activated the client.

 

Thanks.

Sean

0 Replies