Hello,
What I run into at a client:
Users cannot send mail anymore to a lot (not all) contacts listed in the GAL. It shows this error mentioning that the address is not valid anymore and resolves it to the (incorrect) X.400 address. The SMTP address is correct.
They get apx. 30000 contacts pushed into the organization by a GalSync from their main office. A few weeks ago they adjusted something at the main office (and are not very cooperative in finding a solution). Now i see a lot of corrupt X.400 addresses in
the GAL.
I have a PowerShell script to remove all X.400 addresses, but I'm afraid with the next sync, it will be overwritten.
In some way, Outlook 2010 and Exchange 2010 still do some kind of validation against these addresses, while Exchange 2010 does not use X.400 anymore.
So my question is:
Is it possible in Exchange 2010 to disable the X.400 address validation process?

regards,

Peter

Need to support users over the internet? click here try our remote control online beta

Exchange actually does still use that address, the X400/X500 address is used by exchange to route internal mail, so if that address gets changed, all of a sudden users cannot respond to older emails and lots of things quit working. Are these two
offices separate Exchange organizations or the same?

There is an amazing pack of free network admin tools. click here to download it

Hi Russ,
Thanks for the reply.
It concerns two separate Exchange organizations.

Need to support users over the internet? click here try our remote control online beta

Hi
The LegacyExchangeDN is used as an X500 address for routing internally, external routing is done using SMTP except for some government/military solutions. You may need X400 addresses if you have some legacy system that depends on them but Exchange
2010 doesn't use them natively.
Steve

There is an amazing pack of free network admin tools. click here to download it

Are you sure it a X400 and not an X500. Exch doesn't need to use a X400.Sukh

There is an amazing pack of free network admin tools. click here to download it

I worded my response the way I did because most new admins use X400 and X500 interchangeably when talking about Exchange, yes Exchange does not use X400 at all and if you are getting the contacts from another Exchange organization you will need to
find out why the mail is not flowing. Are you receiving NDRs for email, typically if you are sending (replying) to a mail that has an embedded X500 address, you will recieve an NDR with the recipients address resembling the X500 address. Compare
that value to what you are receiving from your galsync, but a key would be to find out what the main office 'tweaked'. But I'm like others here, what makes you think its an X400 address? is it a custom address in the contact?

Need to support users over the internet? click here try our remote control online beta

Hi,
As far as I know, there isn't any way to disable the x400 address validate.
Thanks,

Evan Liu

TechNet Subscriber Support in forum
If you have any feedback on our support, please contact

tngfb@microsoft.com Evan Liu
TechNet Community Support

There is an amazing pack of free network admin tools. click here to download it

Hi All,
Thanks for the replies and explanations.
I am sure it is a X.400 as it is displayed like that in the Email addresses tab of the mailbox properties. The problem was that is was not filled in correctly and showing it with a strikethrough font.

I found a script to remove them, and asked the main office to exclude those addresses from the sync process.
This is running for a few days now and the problem seems to be solved with this work around.
As Russ mentioned, X.500 addresses are used for internal routing, but I don't have these kind of addresses in this organization. Isn't that 'solved' by the use of the 'domain.local' addresses?

There is an amazing pack of free network admin tools. click here to download it

Hi All,
Thanks for the replies and explanations.
I am sure it is a X.400 as it is displayed like that in the Email addresses tab of the mailbox properties. The problem was that is was not filled in correctly and showing it with a strikethrough font.

I found a script to remove them, and asked the main office to exclude those addresses from the sync process.
This is running for a few days now and the problem seems to be solved with this work around.
As Russ mentioned, X.500 addresses are used for internal routing, but I don't have these kind of addresses in this organization. Isn't that 'solved' by the use of the 'domain.local' addresses?

No, that's the default which is created and is different. As is the LegecyDN.Sukh

There is an amazing pack of free network admin tools. click here to download it

You can know more information about x500 address from this document:
Just what is your address?

http://blogs.technet.com/b/exchange/archive/2004/03/24/95451.aspx

Thanks,
Evan Liu



TechNet Subscriber Support in forum
If you have any feedback on our support, please contact

tngfb@microsoft.com Evan Liu
TechNet Community Support

There is an amazing pack of free network admin tools. click here to download it