asked on

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

Hi,

Just did a migration from Server 2003 running exchange 2003 to SBS 2011.

I did things pretty manual. For most of the mailboxes, I just did an exmerge and then uploaded the PST files via PST capture.

I understand that users may/will receive and error when replying to an email from the 'old' server unless they enter the x500 address. I've added the x500 address to a particular account but I figure it might be wrong.

A user tried to send a new email to someone else in the same office and it bounched back straight away with the following:

Delivery has failed to these recipients or groups:

firstname lastname<mailto:IMCEAEX-_O%3Dbusinessorganisation_OU%3DFIRST%2B20ADMINISTRATIVE%2B20GROUP_CN%3DRECIPIENTS_CN%3Dorigin@domain.local> 
The e-mail address you entered couldn't be found. Please check the recipient's e-mail address and try to resend the message. If the problem continues, please contact your helpdesk.







Diagnostic information for administrators:

Generating server: BON-VSBS-01.domain.local

IMCEAEX-_O=businessorganisation_OU=FIRST+20ADMINISTRATIVE+20GROUP_CN=RECIPIENTS_CN=origin@domain.local
#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##

Original message headers:

Received: from BON-VSBS-01.domain.local ([fe80::3cef:11cb:bf8c:967]) by
 BON-VSBS-01.domain.local ([fe80::3cef:11cb:bf8c:967%10]) with mapi id
 14.01.0438.000; Fri, 25 Jan 2013 15:30:10 +1100
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: Firstname Lastname <origin@domain.com.au>
To: Firstname Lastname <destination@domain.com.au>
Subject: test
Thread-Topic: test
Thread-Index: Ac36tKf+LjBTTiVRQT2D1wEb1njIJg==
Date: Fri, 25 Jan 2013 15:30:09 +1100
Message-ID: <491C3C5820C7284E9A785E93B43C430902CF9745@BON-VSBS-01.domain.local>
Accept-Language: en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: <491C3C5820C7284E9A785E93B43C430902CF9745@BON-VSBS-01.domain.local>
MIME-Version: 1.0
X-Originating-IP: [10.1.1.119]

Open in new window

any help would be great thanks

SOLUTION

suriyaehnop

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

suriyaehnop

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Talds_Alouds

ASKER

Thank you very much. That was great.

One other question though.
I started from scratch with the migration and didn't do it via automated methods. As stated, I exported mailboxes with eXmerge.

Did this LegacyExchangeDN issue only occur because I was migrating from exchange 2003? Or, will my next migration for this client, say moving from exchange 2010 to exchange 2013 have the same problems? Thanks

ASKER CERTIFIED SOLUTION

Talds_Alouds

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Talds_Alouds

ASKER

Solution wasn't 100% complete and links didn't provide whole answer.