We are running SBS2011. We had a situation arise where we needed to delete one of our users and recreate a new account for him. His previous username was john and email was john@ourdomain.com.
We created the new user account and gave him the username of jsmith and the hence primary email address of jsmith@ourdomain.com. We then added john@ourdomain.com as an alias so he would continue to receive any emails sent to the old address. This seems to be working for email originating from outside of the company but does not work for anything sent internally to john@ourdomain.com. Our users are not tech savy at all so I am still a little unclear about exactly how they are addressing the emails but I am assuming they are just using the autocomplete functionality in their Outlook programs when they want to send email to John (ie Outlook just autocompletes to "John Smith" <john@ourdomain.com>)
Here is the bounce message that is generated
Diagnostic information for administrators:
Generating server: SVR-SBS2011.sanmateorcd.local
IMCEAEX-_O=FIRST+20ORGANIZATION_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=John+20Smithaa7@ourdomain.local
#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##
Also we did go ahead and add john@ourdomain.local as an alias on his account but that did not help.
Any ideas what is happening and how this might be resolved?
SBSExchange
Last Comment
Gareth Gudger
8/22/2022 - Mon
Gareth Gudger
I would guess that they have old cached entries for this user. See if the problem persists if they try and send from Outlook Web App.
pmckenna11
ASKER
I am sure they are using the cached entries in their Outlooks, what I don't get is that cached entry john@mydomain.com has been created as an alias on the new account jsmith@mydomain.com. I would assume that anything sent internally to john@ would be delivered as this is what happens when someone send an email to john@ from an external source.
I can have everyone delete the old cached entry they have and see what happens but I would like to understand why it doesn't work in the first place
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.