I am getting this error occasionally with a single internaluser. Most of the time I can email this user with no problems. I've tried deleting and recreating the mailbox. All mailboxes are on the same Exchange Server. Exchange 2007 All roles on one server Any tips on troubleshooting this error would be appreciated. Thanks! Subject: Undeliverable: Subject Delivery has failed to these recipients or distribution lists: '<User>'This recipient e-mail address was not found in the recipient e-mail system. Microsoft Exchange will not try to redeliver this message for you. Please check the recipient e-mail address and try resending this message, or provide the following diagnostic text to your system administrator. Sent by Microsoft Exchange Server 2007 Diagnostic information for administrators: Generating server: Servername.Orgname.corp IMCEAEX-_O=FIRST+20ORGANIZATION_OU=FIRST+20ADMINISTRATIVE+20GROUP_CN=RECIPIENTS_CN=user@domainname.com#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ## Original message headers: Received: from Servername.Orgname.corp ([192.168.0.1]) by Servername.Orgname.corp([192.168.0.1]) with mapi; Thu, 14 Jun 2007 08:08:11 -0400Content-Type: application/ms-tnef; name="winmail.dat"Content-Transfer-Encoding: binaryFrom: User2 Displayname <user2@domainname.com>To: User Displayname<IMCEAEX-_O=FIRST+20ORGANIZATION_OU=FIRST+20ADMINISTRATIVE+20GROUP_CN=RECIPIENTS_CN=USER@domainname.com>Date: Thu, 14 Jun 2007 08:08:09 -0400Subject: FW: SubjectThread-Topic: SubjectThread-Index: AceufChByaDtH5NpQTmxmomcFNKoqAAAF2GgMessage-ID: <57E6EC8FBD32CD42BF9A9222569630FD056E90E3C2@Servername.Orgname.corp>Accept-Language: en-USContent-Language: en-USX-MS-Has-Attach:X-MS-TNEF-Correlator: <57E6EC8FBD32CD42BF9A9222569630FD056E90E3C2@Servername.Orgname.corp>MIME-Version: 1.0

This is very weird. It looks like periodically Exchange tries to route this mesage outside of your organization. Check your Outlook nickname file (NK2) and maybe delete it.

Thanks Jim, I'll check that out. I notice that if I manually address to user@domainname.com that it works without fail. What in my post is a clue to you that Exchange is trying to route outside? Does IMEAX indicate internet mail routing or some such? Thanks!

Hi were you able to resolve this issue? we are having exactly the same issue. One thing what i notice, user gets an email internally from another user, and hit reply, outlook puts the username in quotes 'username' and if you double click to see details, you won't see any e-mail addresses linked to that name. usually if it finds the name in the address book, it will underline it. This is just happening randormly. Andy solution to this and why this is happening? any help will greatly appreciate. Delivery has failed to these recipients or distribution lists: 'user'This recipient e-mail address was not found in the recipient e-mail system. Microsoft Exchange will not try to redeliver this message for you. Please check the recipient e-mail address and try resending this message, or provide the following diagnostic text to your system administrator. _____ Sent by Microsoft Exchange Server 2007 Diagnostic information for administrators: Generating server: server1 IMCEAEX-_O=FIRST+20ORGANIZATION_OU=FIRST+20ADMINISTRATIVE+20GROUP_CN=RECIPIENTS_CN=user@domain.com#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ## Original message headers: Received: fromserver.domain.com ([192.168.12.1]) byserver.domain.com ([192.168.12.1]) with mapi; Wed, 4 Jul 2007 09:50:33+0800Content-Type: application/ms-tnef; name="winmail.dat"Content-Transfer-Encoding: binaryFrom:user <user@domain.com>To: 'user' <IMCEAEX-_O=FIRST+20ORGANIZATION_OU=FIRST+20ADMINISTRATIVE+20GROUP_CN=RECIPIENTS_CN=user@domain.com>Date: Wed, 4 Jul 2007 09:50:41 +0800Subject: FW: Message forwaredThread-Topic: Message forware Thread-Index: Ace9IfgkDeKHI/65Qgi0SJBMyyJpOAAu7uXgMessage-ID: 894C86DBED2F1E4F807264E1FF93650A118CD9D02D@server.domain.comAccept-Language: en-USContent-Language: en-USX-MS-Has-Attach:X-MS-TNEF-Correlator: <894C86DBED2F1E4F807264E1FF93650A118CD9D02D@server.domain.com>MIME-Version: 1.0

I have seen this behaviour a fair few times when performing Exchange migrations. In my experience this behaviour occurs due to caching of a users old email address in Outlook. To resolve this you can try the following: Delete the Outlook clients nickname cache file by searching the local Outlook profile for a .NK2 file and deleting it. Change the Outlook tonon-cached mode to ensure it is not a cached entry from the OfflineAddress Book. Check the behaviour in OWA to confirm the server is generating the correct address list and has updated the GAL. Cheers, Rhys

If you migrated the users from 2003 to 2007 doing a cross org migration, Migrating few users at the time.You will have that problem when users are replying to email that were recieved prior to the migration. The simplest way to resolve this problem is add a custom X500 address for each contact that refers to our olg org. /O=oldorg/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=userlias Hope this helps R

Hi: I deleted nk2, created a new profile, OWA is working fine with GAL, Outlook to non-cached, recreate the problem in other station creating new profile and added x500 address with /O=oldorg/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=userlias. Nothing Issue happens randomly, user can send to the users without any problem and users reply him without any problems but once a day or randomly users receive the NDR. thanks L

Dear, Above stated problem can be seen due to multiple factors, may be client Cache is not updated, OAB and GAL is not downloaded/updated or LegacyExchangeDN is missing in the properties of those Mailboxes. you do the following and let me know the results: 1. Delete NK2 file on client side, re-download OAB and GAL from server and use non-cache (online mode) on Outlook, try to send email 2. Open ADSI Edit on the server, browse to the mailbox/contact and check whether LegacyExchangeDN, TargetAddress and ProxyAddress attributes are present? kindly post what is defined in all three attributes. further solution/troubleshooting will be Dependant on these attributes. Regards MYM

Hello All, Please check that the user is not a delegate of another user with an old account. That was my issue. Thanks!

Hello All, Please check that the user is not a delegate of another user with an old account. That was my issue. Thanks! Can you elaborate on this? What do you mean by "old account". I have this issue with a couple users. And of course the 2 or 3 people out of my whole enterprise it is happening to are VIP's...

We are experiencing a similar issue with one of our users. This user was newly created a couple months ago, and was not a migration. Others within Exchange are intermittently receiving a NDR when sending to this user: Delivery has failed to these recipients or distribution lists: 'User' The recipient's e-mail address was not found in the recipient's e-mail system. Microsoft Exchange will not try to redeliver this message for you. Please check the e-mail address and try resending this message, or provide the following diagnostic text to your system administrator. _____ Sent by Microsoft Exchange Server 2007 Diagnostic information for administrators: Generating server: EX-CH-006-SV1.shared.exchangehost.com IMCEAEX-_O=IHOST_ou=Exchange+20Administrative+20Group+20+28FYDIBOHF23SPDLT+29_cn=Recipients_cn=user+5Fdomain+2Ecom@shared.exchangehost.com #550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ## We have made sure that the Outlook nk2 files are cleared and have even cleared the recent recipient list in OWA. As an additional bit of evidence that this is being caused server-side, we set up a new Entourage EWS connection on a computer that had never previously been connected to this domain. When a new message is created and the effected user's name is entered, the contacts and recent addresses suggestion window lists two entries for that user: one with his proper SMTP email address, and one with the X.500 address listed above. Is there anything we can check to try and find where this erroneous entry is coming from?

We are also experiencing this issue, when a user creates a cal appointment and sends it to a DL they are recieving a bounce but the user in the bouce was never part of the DL.

We are also experiencing this issue, when a user creates a cal appointment and sends it to a DL they are recieving a bounce but the user in the bouce was never part of the DL. Make sure that the user listed in the bounce is not listed as a delegate for any of the users that are part of the DL. Also make sure that none of the DL user's have their calendars shared with that bounce recipient. I saw this exact circumstance before with another customer, and they swore up and down that they had removed the user from any DLs, shares and delegates. I loaded up Outlook for one of the DL members and sure enough, the removed user was listed as a delegate. Delegation and permissions do not get removed automatically when a user is removed from Exchange. http://www.vardynamics.com/

We have had the same issue and found that OWA works fine while Outlook will fail. An existing users mailbox is removed and recreated. Many are able to send to the user but others fail. I have found that the ones that fail are only those that have sent messages to that user previously and it only applies to Outlook not OWA. It seems like there are conflicting entries for the replaced mailbox in senders Outlook cache, so sometimes it goes thru, while other times it fails. Switching off cached exchange mode sometimes corrects the issue, but not in all cases. Replacing the Outlook profile of users who receive the message has corrected the issue each time so far. Hope this helps

On Fri, 7 Jan 2011 15:49:48 +0000, goflyfishin wrote: > > >We have had the same issue and found that OWA works fine while Outlook will fail. > >An existing users mailbox is removed and recreated. Many are able to send to the user but others fail. I have found that the ones that fail are only those that have sent messages to that user previously and it only applies to Outlook not OWA. The value of the user's legacyExchangeDN property are different now to what they were before. The "address completion cache" on Outlook is the most common (but no the only) cause of this. You can make this symptom do away pretty easily by adding the old legacyExchangeDN value to the "E-Mail Addresses" tab on the user. Pick "X500" as the address type. >It seems like there are conflicting entries for the replaced mailbox in senders Outlook cache, so sometimes it goes thru, while other times it fails. Switching off cached exchange mode sometimes corrects the issue, but not in all cases. Replacing the Outlook profile of users who receive the message has corrected the issue each time so far. It may be the address completion cache, or it may be that the OAB hasn't been updated (or downloaded by the client), or that the problem happens when they reply to an e-mail sent by that mailbox before the legacyExchangeDN value changed. If the OAB is the problem you should address that. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi guys, I had the same issue with migrated users who we imported to our exchange server. The trick with nk2 file and checking the experience in OWA highlighted they were using outdated nicknames when sending emails. Also the point about delegate access; we had that for a different issue - Users who were imported from one exchange server, who had delegate access on their account had latent permissions on their account which were not showing up. We added delegate access again and then removed it; resolved all notification errors.

On Fri, 7 Jan 2011 15:49:48 +0000, goflyfishin wrote: > > >We have had the same issue and found that OWA works fine while Outlook will fail. > >An existing users mailbox is removed and recreated. Many are able to send to the user but others fail. I have found that the ones that fail are only those that have sent messages to that user previously and it only applies to Outlook not OWA. The value of the user's legacyExchangeDN property are different now to what they were before. The "address completion cache" on Outlook is the most common (but no the only) cause of this. You can make this symptom do away pretty easily by adding the old legacyExchangeDN value to the "E-Mail Addresses" tab on the user. Pick "X500" as the address type. >It seems like there are conflicting entries for the replaced mailbox in senders Outlook cache, so sometimes it goes thru, while other times it fails. Switching off cached exchange mode sometimes corrects the issue, but not in all cases. Replacing the Outlook profile of users who receive the message has corrected the issue each time so far. It may be the address completion cache, or it may be that the OAB hasn't been updated (or downloaded by the client), or that the problem happens when they reply to an e-mail sent by that mailbox before the legacyExchangeDN value changed. If the OAB is the problem you should address that. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP I know this is an old thread, but being this is the first time posting here, I am not sure how to find current threads yet. Your suggestion is something I wanted to try, but the address type only allows for SMTP. How can I change this? "The value of the user's legacyExchangeDN property are different now to what they were before. The "address completion cache" on Outlook is the most common (but no the only) cause of this. You can make this symptom do away pretty easily by adding the old legacyExchangeDN value to the "E-Mail Addresses" tab on the user. Pick "X500" as the address type." Edited to add that the issue is resolved. Your advice worked, my understanding of how to include an X500 address wasw the final hurdle to overcome.

have been running into this same issue with one user in my org. I migrated from 2003 to 2007, and slowly, for different users in my domain, the nk2 file/autocomplete keeps trying to send mail to a mailbox that was briefly set up, then deleted, as I misspelled the users last name. I honestly have no idea how the two mailboxes have been linked, and it is driving me insane, as I have been all through ASDIEdit looking for the old value of the misspelled entry, and I cannot find it. Here is the laundry list of where I am at/detailed description: valid username is jdoe, old misspelled entry is gdoe (obviously sanitized) Problem is when users pull from GAL/Outlook autocomplete, Outlook shows jdoe@domain.com, but exchange tries to send it to gdoe@domain.com gdoe is not associated with the user in ASDIEdit under LegacyExchangeDN I have assigned the user an x500 address of gdoe, no avail. I have tried deleting nk2 files, moving the GAL server around, set users to not run outlook cached mode, redownloaded the OAB, and still nothing. Once a user has the missasociated address, they are unable to email the proper address, unless they use an alias that I have set up. Can anyone point me to a tool that will scrape all of ASDIEdit for a value, so maybe I can find where this rogue entry lives?

did you update the GALs and OABs?

I am having a similar issue. Was this resolved? When I send a meeting request to a specific user, he gets the request but I get the Delivery has failed message from a user that is no longer with the company and account does not exist anymore. Both OWA and Outlook have are doing it.

My company has the exchange servers configured not to receive Active Directory updates. Consequently when you update email addresses in AD, and not in the Exchange Management Console, any emails sent using the updated AD distribution lists would fail. We received reports of these failures and noticed that one of our outside contacts had his contact information removed from the Exchange Management Console. By adding the information back into Exchange and ensuring it was identical to the AD information, the emails would go through and the failure messages ceased. Just make sure you wait for replication to be processed by all the servers.C5rookie

Hi, There will be a legacy exchange dn name in the place of display name, when you will see the quoted user property. Like " /o=Example/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=juser" put this as x500 id in that user's mailbox. To create X500 id create a custome address in user's mailbox. I hope it will be helpfull for you. Regards, Jitendra Kumar Singh Progressive Infotech Pvt. Ltd.

Hi, I am getting a [NEWSENDER] word attached in the subject field whenever any user get some bounce back from our one of cas,ht server. Actually we have deployed the cas and ht role on same pc and we have two server having same role running in NLB mode. can somebody tell me why [NEWSENDER] word is getting attached in subject field. While when we receive the bounce back from second node of NLB then that will be normal bounse back message. ThanksRegards, Jitendra Kumar Singh Progressive Infotech Pvt. Ltd.

I use this tool and it works pretty well. Good for those users who absolutely cannot lose this file: NK2 Edit

NK2 Edit...Nice and Handy tool. Thanks for info.

We had this same issue but it was related to a user who delegated their calendar to a user who was no longer with the company and her mailbox was removed. Our issue was a little different, users would receive a NDR relating to a user who's mailbox had been removed. We first looked for a forward to a distro group but didn't find anything. Then we checked for delegates on the calendar, boom, he had delegated his calendar to an exec admin that was no longer with our firm. Hope this helps!!

So we just did a pilot group to Office 365 and once our small group was migrated it turns out that users within our organization that use a variety of Office outlook 2010 an d2007 couldn't email and they would receive a bounced message: The recipient's e-mail address was not found in the recipient's e-mail system. Microsoft Exchange will not try to redeliver this message for you. Please check the e-mail address and try resending this message, or provide the following diagnostic text to your system administrator. _____ Sent by Microsoft Exchange Server 2007 So we have an internal 2003 exchange server (primary) and a 2010 exchange server that sync's with the 2007 exchange server fyi. Once we migrated our pilot group members we couldn't receive any emails. We then had to change our accounts to Mail Enabled contacts from our 2010 exchange server but then had the issue described below. What I did to correct this issue is on the user's 2007 outlook changed it from cached exchange mode to noncached and emailed one of our pilot group members with out error. I then changed it back to cached exchange mode and tested successfully again. Anyone know why this would work like this?

I'm sorry I'm late to this topic but I'm starting to see this problem when responding to a specific room email we have setup in our Exchange 2007 system. I have three users that one runs MAC OS with Office 2010, Windows 7 with Office 2010, and one with XP Pro and Office 2007. The room in question sends out a meeting request/calendar request. When the users in question respond they see the following. ..Any advice would be helpful.. User 1: Windows 7 office 2010 Delivery has failed to these recipients or distribution lists: Board Room Your message wasn't delivered because of security policies. Microsoft Exchange will not try to redeliver this message for you. Please provide the following diagnostic text to your system administrator. _____ Sent by Microsoft Exchange Server 2007 Diagnostic information for administrators: Generating server: TOWERS.company-int.com BoardRoom@company.com #550 5.7.1 RESOLVER.RST.NotAuthorized; not authorized ## Original message headers: Received: from TOWERS.company-int.com ([172.16.1.167]) by TOWERS.company-int.com ([172.16.1.167]) with mapi; Thu, 28 Jun 2012 14:36:59 -0600 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: binary From: M <m@company.com> To: Board Room <BoardRoom@company.com> Date: Thu, 28 Jun 2012 14:36:48 -0600 Subject: Accepted: R standup meeting Thread-Topic: Accepted: R standup meeting Thread-Index: Ac1VbcMmk6xma30XRVqcvAnUzYWO/A== Message-ID: <1A0963DA-04CC-43B0-9E97-59C32360D4D5@company.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: <1A0963DA-04CC-43B0-9E97-59C32360D4D5@compnay.com> MIME-Version: 1.0 User 2: MAC Office 2010 From: Microsoft Exchange <MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e@company.com> Subject: Undeliverable: Accepted: R standup meeting Date: June 28, 2012 3:16:15 PM MDT To: E <e@company.com> Delivery has failed to these recipients or distribution lists: Board Room Your message wasn't delivered because of security policies. Microsoft Exchange will not try to redeliver this message for you. Please provide the following diagnostic text to your system administrator. Sent by Microsoft Exchange Server 2007 Diagnostic information for administrators: Generating server: TOWERS.company-int.com BoardRoom@company.com #550 5.7.1 RESOLVER.RST.NotAuthorized; not authorized ## Original message headers: Received: from TOWERS.company-int.com ([172.16.1.167]) by TOWERS.company-int.com ([172.16.1.167]) with mapi; Thu, 28 Jun 2012 15:16:15 -0600 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: binary From: E <e@company.com> To: Board Room <BoardRoom@company.com> Date: Thu, 28 Jun 2012 15:16:14 -0600 Subject: Accepted: R standup meeting Thread-Topic: R standup meeting Thread-Index: Ac1Vcz+vCSHopU+LS62q4utsydPhvA== Message-ID: <EB2BB7AB2B0F2148AAECB2314BA3F4BA6CBB4320E2@TOWERS.company-int.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: <EB2BB7AB2B0F2148AAECB2314BA3F4BA6CBB4320E2@TOWERS.company-int.com> MIME-Version: 1.0 Reporting-MTA: dns; TOWERS.company-int.com Final-recipient: RFC822; BoardRoom@company.com Action: failed Status: 5.7.1 X-Supplementary-Info: < #5.7.1 smtp;550 5.7.1 RESOLVER.RST.NotAuthorized; not authorized> X-Display-Name: Board Room From: E <e@company.com> Subject: Accepted: R standup meeting Date: June 28, 2012 3:16:14 PM MDT To: Board Room <BoardRoom@company.com> User 3 XP Pro Office 2007 Delivery has failed to these recipients or distribution lists: Board Room Your message wasn't delivered because of security policies. Microsoft Exchange will not try to redeliver this message for you. Please provide the following diagnostic text to your system administrator. _____ Sent by Microsoft Exchange Server 2007 Diagnostic information for administrators: Generating server: TOWERS.company-int.com BoardRoom@company.com #550 5.7.1 RESOLVER.RST.NotAuthorized; not authorized ## Original message headers: Received: from TOWERS.company-int.com ([172.16.1.167]) by TOWERS.company-int.com ([172.16.1.167]) with mapi; Thu, 28 Jun 2012 14:47:25 -0600 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: binary From: J <J@company.com> To: Board Room <BoardRoom@company.com> Date: Thu, 28 Jun 2012 14:47:19 -0600 Subject: Accepted: R standup meeting Thread-Topic: R standup meeting Thread-Index: Ac1VbaQU4RABRGMRS56GA6ho5tiHAwAAZFVw Message-ID: <EB2BB7AB2B0F2148AAECB2314BA3F4BA6CBB7FDEBB@TOWERS.company-int.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: <EB2BB7AB2B0F2148AAECB2314BA3F4BA6CBB7FDEBB@TOWERS.company-int.com> MIME-Version: 1.0

Its simple. Download NK2 edit tool. its a small and nice tool. Browse to nk2 file and see DN of any existing/healthy user like for me its /O=HYPERQUALITY/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=PRAMOD.DIXIT but the problematic user is shummy.ahuja so replace it like /O=HYPERQUALITY/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=SHUMMY.AHUJA now add this DN as X500 address in users Email address property in exchange and enjoy.. Pramod Dixit..Lead System Engineer..Hyperqualiy Inc.Pramod Dixit