Avatar of padas6
Flag for India asked on

Exchange contcat issue

Hi Team,

We have Exchange server 2007 environment, but we have multiple domain but having common GAL for using OCS which is located one domain.

Currently we are facing issue in one domain, when user is sending a mail to other domain it is resolving the id as per below,

#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##

Note: User is sending a mail from x.com to y.com domain but id is resoved as x.com as recipient having contact in x domain & user mailbox in y domain. ( both are in common GAL)

Avatar of undefined
Last Comment

8/22/2022 - Mon
Manpreet SIngh Khatra

Are you saying one user has

Which is Primary ? Always an email comming to the user will show email comming to "UserName@a.com" so if you want to understand if the email is comming for a.com or b.com you need to have Outlook rule for Header of an email

- Rancy
Rajkumar Duraisamy

If it is a single user issue.. ask that user to clear the outlook auto cache entry for the failed email address and ask him to manually type the full email address and check the status

First of all this is not relate to Primary or Secondary email ID & this issue happeing with couple of users.

We have 4 separete domain & using common GAL for using OCS . so that means a user nane test1@a.com user having contact is @test1@b.com, test1@c.com & test1@d.com.

so when a user from @a.com send a mail to @b.com it is resolving as per below,

IMCEAEX-_O=NT5_ou=f3083da5f2f44c4dacd99e5e9d9c9e80_cn=09c90eb05cabbd498a3e2b3aea032205@a.com ( as @b.com user having contcat in @a.com).

Hope it is clear the undersanding.

Please let  me know for any further information needed.
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck
Manpreet SIngh Khatra

Does the same Happen if they use OWA .... as it could be cache issue as well

- Rancy

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
Learn why we charge membership fees
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.
ask a question

sorry to all, I was in different issue.

This is only happen only outlook only , but we have tried below things still problem persists,

1. Create a new profile by deleting old .nk2 file in user profile.
2. Create a new profile in other laptop.
3. reinstall outlook.
4. Reinstall os as well :)

Sometimes it is resolve the deleting entirely nk2 file ,but I think something we have to do.

One point I am not able to understand, my legacy Exchange is showing as per below,

/o=xyz/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=dasp

same addreess I have to create in X500 connector , please confirm.

/o=xyz/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=dasp@x.com

Note : I have checked email Email Addres & we are using x400 not x500.

sorry contact having x500 email address & mailbox user having only x400 email address .
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.

Basically this happen when the contact objects get recreated or somehow the legacyExchangeDN  of the object changes – We are just adding the old legacyExchangeDN as a X500 address to the new Contact to fix this NDR. It's added as a Custom Address as shown in screenshot…X500
For example if you have issue sending mail to contact dasp@x.com and you are getting IMCEAEX-_O=XXXXXXXXXXXXXXX@x.com email address in NDR..

Which converts to

/o=xyz/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=dasp@x.com

Then you need to add the above converted address as a X500 address to the contact.

Yes , this was the issue with X500 connctor.