Hybrid: Changing MX Record to Office365 - internal relay domain - not all mail addresses in cloud

%3CLINGO-SUB%20id%3D%22lingo-sub-905191%22%20slang%3D%22en-US%22%3EHybrid%3A%20Changing%20MX%20Record%20to%20Office365%20-%20internal%20relay%20domain%20-%20not%20all%20mail%20addresses%20in%20cloud%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-905191%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20everyone%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ewe%20want%20to%20change%20our%20MX%20record%20to%20Office%20365.%20We%20run%20a%20hybrid%202013%20scenario.%20The%20on%20prem%20server%20is%20configured%20with%20internal%20relay%20so%20that%20recipients%20not%20found%20in%20our%20installation%20is%20forwarded%20to%20another%20server.%3C%2FP%3E%3CP%3EIn%20the%20cloud%20we%20get%20a%20NDR%20because%20of%20the%20DBEB.%20I%20could%20not%20find%20the%20switch%20to%20change%20it%20to%20%22off%22.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAim%20is%3A%3C%2FP%3E%3CP%3EThat%20an%20address%20not%20found%20is%20forwarded%20through%20the%20connector%20to%20on%20premise%20and%20from%20there%20forwarded%20to%20the%20other%20system.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDo%20i%20have%20to%20create%20a%20contact%2Fmailuser%20for%20every%20mail%20address%20that%20the%20other%20system%20holds%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%20regards%3C%2FP%3E%3CP%3EStephan%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-905191%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2013%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-907107%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%3A%20Changing%20MX%20Record%20to%20Office365%20-%20internal%20relay%20domain%20-%20not%20all%20mail%20addresses%20in%20clou%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-907107%22%20slang%3D%22en-US%22%3E%3CP%3ETo%20toggle%20DBEB%20off%2C%20switch%20the%20domain%20to%20Internal%20Relay%20(EAC%20-%26gt%3B%20Mail%20Flow%20-%26gt%3B%20Accepted%20domains%20-%26gt%3B%20double-click%20the%20domain).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-909486%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%3A%20Changing%20MX%20Record%20to%20Office365%20-%20internal%20relay%20domain%20-%20not%20all%20mail%20addresses%20in%20clou%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-909486%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F58%22%20target%3D%22_blank%22%3E%40Vasil%20Michev%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi.%20Thanks%20for%20your%20answer.%20It%20was%20just%20a%20time%20problem.%20After%2030%20minutes%20it%20started%20working%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

Hi everyone,

 

we want to change our MX record to Office 365. We run a hybrid 2013 scenario. The on prem server is configured with internal relay so that recipients not found in our installation is forwarded to another server.

In the cloud we get a NDR because of the DBEB. I could not find the switch to change it to "off".

 

Aim is:

That an address not found is forwarded through the connector to on premise and from there forwarded to the other system. 

 

Do i have to create a contact/mailuser for every mail address that the other system holds?

 

Best regards

Stephan

2 Replies

To toggle DBEB off, switch the domain to Internal Relay (EAC -> Mail Flow -> Accepted domains -> double-click the domain).

@Vasil Michev 

Hi. Thanks for your answer. It was just a time problem. After 30 minutes it started working