Exchange try to deliver local instead offer smart-host for deleted/changed email address

%3CLINGO-SUB%20id%3D%22lingo-sub-1179872%22%20slang%3D%22de-DE%22%3EExchange%20try%20to%20deliver%20local%20instead%20offer%20smart-host%20for%20deleted%2Fchanged%20email%20address%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1179872%22%20slang%3D%22de-DE%22%3E%3CP%3EHi%3CBR%20%2F%3EDon't%20really%20know%20if%20this%20is%3CBR%20%2F%3Ethe%20right%20place%20to%20ask%2C%20but%20I%20have%20a%20problem%20with%20our%20newly%20set%20up%20Exchange%20Server%20(2016)%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EWe%20have%20internal%20and%20external%20personnel%2C%20so%20I%20set%20the%20Exchange%20up%20as%20an%20internal-relay%20and%20a%20smart-host%20for%20sending.%20It%20works%20fine.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EInternal%20users%20have%20the%20email%20address%20user%40domain.com%20registered%20in%20exchange%3CBR%20%2F%3EExternal%20users%20have%20the%20email%20address%20ex.user%40domain.com%20registered%20in%20Exchange.%20(The%20messages%20here%20are%20only%20forwarded%20to%20a%20different%20mailbox%20to%20archive%20them.%20Their%20normal%20email%20address%20(user%40domain.com)%20is%20not%20registered%20in%20exchange.)%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EIt%20worked%20all%20fine.%20But%20now%20I%20wanted%20to%20switch%20user1%20from%20internal%20to%20external.%3C%2FP%3E%3CP%3ESo%20I%20disabled%20the%20mailbox%20and%20made%20a%20new%20one%20fort%3CBR%20%2F%3Ethe%20same%20user%20with%20the%20external%20address%20(ex.user1%40domain.com)%20If%20internal%20users%20email%20that%20user%20with%20the%20address%20user1%40domain.com%20it%20should%20go%20over%20the%20smart%20host%2C%20because%20there%20is%20no%20user%20anymore%20with%20this%20address.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EBut%20I%20get%20this%20error%20message%3A%3CBR%20%2F%3ERemote%20Server%20returned%20'550%205.1.11%20RESOLVER.%20Cor.%20%3CSPAN%20class%3D%22hiddenGrammarError%22%3EExRecipNotFound%3C%2FSPAN%3E%3B%20Recipient%20not%20found%20by%20Exchange%20Legacy%20encapsulated%20email%20address%20lookup'%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EI%20tried%20to%20delete%20the%20%3CSPAN%20class%3D%22hiddenSpellError%22%3ElagacyExchangeDN%3C%2FSPAN%3E%20continued%20that%20user%20in%20the%20AD%2C%20but%20it%20keeps%20refilling%20it%20and%20I%20don't%20really%20know%20what%20else%20to%20try.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EI%20basically%20want%20the%20user1%40domain.com%20gone%20from%20exchange%2C%20so%20he%20sends%20emails%20for%20that%20user%20over%20the%20smart-host%20and%20don't%20try%20to%20deliver%20it%20locally%20but%20somehow%20the%20address%20is%20still%20linked%20tot%20has%20user.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1179872%22%20slang%3D%22de-DE%22%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Occasional Visitor

Hi
Don't really know if this is the right place to ask,
but I have a problem with our newly set up Exchange Server (2016)


We have internal and external personal, so I set the Exchange up as an intern-relay and a smart-host for sending. It works fine.


Internal users have the email address user@domain.com registered in exchange
External users have the email address ex.user@domain.com registered in Exchange. (The messages here are only forwarded to a different mailbox to archive them. Their normal email address (user@domain.com) is not registered in exchange.)


It worked all fine. But now I wanted to switch user1 from internal to external.

So I disabled the mailbox and made a new one fort the same user with the external address (ex.user1@domain.com)
If internal users email that user with the address user1@domain.com it should go over the smart-host, because there is no user anymore with this address.


But I get this error message:
Remote Server returned '550 5.1.11 RESOLVER.ADR.ExRecipNotFound; Recipient not found by Exchange Legacy encapsulated email address lookup'


I tried to delete the lagacyExchangeDN fort that user in the AD, but it keeps refilling it and I don't really know what else to try.


I basically want the user1@domain.com gone from exchange, so he sends emails for that user over the smart-host and don't try to deliver it local but somehow the address is still linked tot hat user.

1 Reply
Highlighted

@hiddsd 

 

I am unsure what you are doing with the old email address, user1@domain.com, after converting them to ex.user1@domain.com.

 

I would have maintained the old address user1@ domain.com by adding it as a secondary address to ex.user1@ domain.com.  I would have documented the legacyExchangeDN on the user1@ domain.com mailbox and added it as a x500 address to the ex.user1@ domain.com mailbox.  But you deleted the user1@ domain.com mailbox so you can't get the legacyExchangeDN now.

 

However, with all that said what it sounds like you are having an issue with is the autocomplete entry.  Try clearing that in Outlook when creating a new message.  Start typing the recipients name, you should see the users name show up, click the X to delete the entry.  Next, choose the user from the GAL or try typing the new email address in full.  You'll have to do that for everyone individually.  If you carried over the legacyExchangeDN from the old mailbox you would not have to do this.