How to Edit and Add a Legacy X500 Address Into The New Mailbox

Riaz Alexander AnsaryEnterprise Infrastructure Systems Engineer
CERTIFIED EXPERT
Published:
Updated:
Edited by: Andrew Leniart
There might be times that you will need to associate an SMTP address from one mailbox to another within your exchange organization. You then notice that your help desk start to receive complains that messages sent to that mailbox by some people bounce back. Let's talk about the issue.

If for any reason if you move an SMTP address from one mailbox to another, your  help desk start to receive complains that certain users (Not All) receive the following bounce backs when sending messages to that mailbox:



Here is the reason for this bounce back:


Internal exchange messages inside the organization normally have the recipient’s information resolved to LegacyExchangeDN attribute (Underlined in Red). 


In this case since this address was assigned to a different mailbox the old LegacyExchangeDN value is changed; so, if a user who has sent an email to that address that was associated with the old mailbox sends an email after the change, they will get this bounce back because the LegacyExchangeDN value is cached on their outlook. There is no problem for people who never sent to that address before.


Now if you see the bounce back Diagnostic Information message above you see that it provides you with the Legacy Exchange DN (Boxed in Red), Or you can access that by clicking on the name in the body of bounce back message:


IMCEAEX-_o=COSTARGROUP_ou=Exchange+20Administrative+20Group+20+28FYDIBOHF23SPDLT+29_cn=Recipients_cn=8da2b5094c364af7bb8861ce9064020a-ransnary@domain.com


We need to add the above X500 to the new mailbox, the tricky part is that the above x500 is in an encoded (Messed Up) format and we need to clean up to bring it to the right format. here is how it's done


Step-by-step guide


  1. Get rid of the _ and replace it with


/o=COSTARGROUP/ou=Exchange+20Administrative+20Group+20+28FYDIBOHF23SPDLT+29/cn=Recipients/cn=8da2b5094c364af7bb8861ce9064020a-ransnary@domain.com


    2. As you can see you will notice some numbers like +20,+28,+29

        Convert +20 with a Space

        Convert +28 with a (

        Convert +29 with a )

        Convert +2E with a .


So now, replace the values as described and you should get the following:

/o=COSTARGROUP/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=8da2b5094c364af7bb8861ce9064020a-ransary@domain.com


    3. Remove the @Domain.com and just keep the username

/o=COSTARGROUP/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=8da2b5094c364af7bb8861ce9064020a-ransary

Now simply add the final cleaned up proper x500 address to the mailbox via exchange management shell:


Set-Mailbox -Identity ransary -EmailAddresses @{Add = 'X500:/o=COSTARGROUP/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=8da2b5094c364af7bb8861ce9064020a-ransary'}


Sometimes you may need to update the legacyexchagedn attribute itself as well. unlikely but I have run into that situation as well. 



0
19,882 Views
Riaz Alexander AnsaryEnterprise Infrastructure Systems Engineer
CERTIFIED EXPERT

Comments (1)

WORKS2011Managed IT Services, Cyber Security, Backup

Commented:
Do I clean up the email address just prior to the @.

In the example below there's a 268 after the users email address. The actual email address is johndoe@mydomain.com  not johndoe268@mydomain.com

John Doe
-/O=FIRSTORGANIZATION/OU=EXCHANGEADMINISTRATIVEGROUP(FYDIBOHF23SPDLT)/CN=RECIPIENTS/CN=JohnDoe268

Have a question about something in this article? You can receive help directly from the article author. Sign up for a free trial to get started.

Get access with a 7-day free trial.
You Belong in the World's Smartest IT Community