I had two mailboxes that would not move from a corrupted E2010 datastore to another. I ended up exporting the mailbox to a PST. Deleting the current E2010 mailbox. Creating a new one on a different datastore and importing the PST. Everything works well but there have been a few instances of people getting undeliverables to the 2 mailboxes that went through this procedure. Some left over garbage to clean up? There are no errors on the server side and only the bounce back message on the server side. I did have the sender pull the name from the GAL instead of the local address book. Same result, unless he replies to an e-mail from me (which works fine). It just so happens the user is my boss and one of the mailboxes that were imported is mine. He is using Outlook 2007. Thoughts anyone?

It only occurs for a few users and for the one user we tested, it happens pulling the address from the GAL via Outllok 2007 client and also happens with OWA.

Here is the undeliverable bounce back e-mail that is generated when it fails. Delivery has failed to these recipients or groups: Receiver 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: ClientAccess2.Company.local IMCEAEX-_O=COMPANY+20COMPANYNAME+20TESTOFCONAME_OU=First+20Administrative +20Group_cn=Recipients_cn=receiver@company.com #550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ## Original message headers: Received: from MB1.Company.local ([fe80::1d1e:7b3:5e9d:b01a]) by ClientAccess2.brickstreet.local ([fe80::bc4e:fb4a:aa5a:fb7%11]) with mapi id 14.01.0270.001; Fri, 14 Jan 2011 15:34:51 -0500 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: binary From: "Sender" <sender@brickstreet.com> To: "Receiver" <receiver@brickstreet.com> Subject: Test Thread-Topic: Test Thread-Index: Acu0Kn10t8L6+L2/QSCU2AaylzVGkg== Date: Fri, 14 Jan 2011 15:35:21 -0500 Message-ID: <6D0E2DBB307F384488906D1589C27001AF9148@MB1.company.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: <6D0E2DBB307F384488906D1589C27001AF9148@MB1.company.local> MIME-Version: 1.0 X-Originating-IP: [1.2.3.4]

When you deleted the old mailbox, Active Directory would have been updated with the nullified homemdb attributes. Then when you made a new mailbox it would have filled this attribute in with the new server. The Hub Transport’s categorizer is what’s responsible for figuring out this sort of mail delivery (not the old mailbox server) so unless there is something stale or not properly replicating in AD, there should be no dependency on the mailbox server. You said it also happens with OWA. Are you sure OWA isn’t using the autocomplete, or you’re not replying to an old message with a bad x400 in the replyto field? Manually typing the SMTP address – does that work? Mike Crowley Check out My Blog!

Also, when you say “corrupted datastore”; what does this mean? Do you have an orphaned database or mailbox server in your org? Mike Crowley Check out My Blog!

Hi billio, Any updates on your issue? Please also see this similar post: Exchange 2007 - delete / recreate mailbox now giving NDR's http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/aecf111a-5fcf-4638-b030-ec4200f45f54/Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Adding a X500 address per the post below fixed my issue. Thanks to all. http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/aecf111a-5fcf-4638-b030-ec4200f45f54/?prof=required

Great! (this is what I asked about initially J) Mike Crowley Check out My Blog!