Improve company productivity with a Business Account.Sign Up

x
?
Solved

convert or translate or reroute for legacy x.400 addresses

Posted on 2009-04-10
5
Medium Priority
?
2,203 Views
Last Modified: 2012-06-27
Good Afternoon Everyone,

Here is my situation:

Current Exchange 2007 Environment has 1 CA/HUB server, 3 MB Servers, and 1 legacy 2003 server.

Uninstalled a legacy 2003 server from the environment, and followed all of the steps appropriately.  Uninstalled Exchange, then deleted the Administrative Group since it was now empty.  Unfortunately, up until that point, the default email address was the x.400 address, which was invalidated when I removed the Legacy Administrative Group.  I have since reset the Address Recipient policy, re-applied it, and rebuilt the OAB and forced a download.  

My remaining problem is that any time a user replies to an old email, it defaults with the x.400 address and generates an NDR with the following error:

IMCEAEX-_O=<Exchange Org Name>_OU=<Deleted Legacy Admin Group>_CN=<User's AD OU>_CN=<AD OU>_CN=user@domain.com
#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##

What I'm looking for is a way to make the old x.400 addresses valid again.  I tried to create a transport rule and strip the 'IMCEAEX' Etc out of the header, and that didn't work.  I also tried to create a send connector that was an x.400 pointing to the smtp.domain.com SMTP address, and that didn't work either.  I just need to make these old legacy email addresses work.

Regards,
Rev
0
Comment
Question by:revgroup
  • 4
5 Comments
 
LVL 1

Author Comment

by:revgroup
ID: 24131992
I would settle for a way to configure my Outlook clients to ignore x400 addresses and default to the SMTP addresses at this point.  I don't have any additional informaiton to add to this post at this point.
0
 
LVL 15

Accepted Solution

by:
abhaigh earned 2000 total points
ID: 24137308
The native addressing format for Exchange is X500

if you know what the old X400 addresses are, just add them to the email addresses tab for the user's profile - that should sort things out

however, if the system is looking for the X500 address - you'll need to add it to the email addresses tab in order for the mail to reach the right location - for that you'll need to know the old LegacyExchangeDN for the old mailboxes
0
 
LVL 1

Author Comment

by:revgroup
ID: 24137840
Good Morning,

Got this sorted out with Microsoft.  We ended up using ADModify to add in the x500 address entry using this post as a reference:

http://msexchangetips.blogspot.com/2008/01/exchange-bulk-remove-x400-address-using.html

The actual syntax of the entry on the "Custom" Tab of ADModify was as follows:

Attribute Name: proxyAddresses
Attribute Value: x500:/o=<Exchange Organization>/ou=<Legacy Admin Group>/cn=Recipients/cn=%'MailNickname'%

Also, I selected "Multivalued Append" instead of "Multivalued Remove" as discussed in the above post.

It is important to put those ticks in there around MailNickname.  Without them, it will just insert MailNickname which could cause a wealth of problems since there aren't any duplication checks when you use ADModify and you could end up with hundreds of users with the same x500 address.  

ALSO BEWARE, if you attempt to remove x500 addresses from the custom tab (removing x400 only removed x400 addresses), it will remove ALL, I repeat ALL alias email addresses from your target users.  Make sure you have your Address Policies in order, and re-apply them immediately after you strip out all of the attributes if necessary.  See this post for reference on how to set up Email Address Policies:

http://www.petri.co.il/defining-exchange-2007-email-address-policy-part-2.htm

The beauty of using ADModify instead of the GUI in EMC is that it will not set the x500 as a default or reply address, this will prepare your organization to remove x400 and x500 addresses alltogether since email replies won't default to the x500.
0
 
LVL 1

Author Comment

by:revgroup
ID: 24137864
Abhaigh,

Sorry, I forgot to clarify.  We had changed the LegacyExchangeDN using ADSIEdit becuase Free/Busy data wasn't available.  Since that had been changed, the x400 addresses were pointing nowhere.  Adding the x500 addresses did the trick.

Regards,
Rev
0
 
LVL 1

Author Closing Comment

by:revgroup
ID: 31569050
See Post below for complete method of applying the solution to multiple users.  Thanks Abhaigh!
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

In migration, Powershell can be a very crucial tool to achieve success and finalize projects within deadline or even fix issues. X500 or Legacy Exchange DN Attribute can cause lots of issue during the migration
Lotus Notes is the most prominent choice of all users due to its advance email management. It provides email features along with contact management, appointments, task, calendar etc. Many users rely on its service to carry out electronic communicati…
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
Watch the video to know how one can repair corrupt Exchange OST file effortlessly and convert OST emails to MS Outlook PST file format by using Kernel for OST to PST converter tool. It can convert OST to MSG, MBOX, EML to access them. It can migrate…

595 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question