When booking a meeting to a exchange 2010 user we get failed delivery
This problem happens if an internal or external person tries to book a meeting to ONE specific person the company. When I send a meeting request to MCzajkowski it fails and says that the user is not found.. but the user it lists is from an old exchange server. The errror says that and old user (does not exist anymore) can not be found.. I can NOT see where the current new user is mapped to anything from an old user in an OLD exchange box that isn't running anymore. Delivery has failed to these recipients or groups: Dave EDI The e-mail address you entered couldn't be found. Check the address and try resending the message. If the problem continues, please contact your helpdesk. Diagnostic information for administrators: Generating server: crimzonrose.com IMCEAEX-_o=CrimzonRose_ou=First+20Administrative+20Group_cn=Recipients_cn=csouza@crimzonrose.com #550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ## To: Dave EDI <IMCEAEX-_o=CrimzonRose_ou=First+20Administrative+20Group_cn=Recipients_cn=csouza@crimzonrose.com> 550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ## Original message headers: Received: from EXCHANGE2010.crimzonrose.domain ([::1]) by EXCHANGE2010.crimzonrose.domain ([::1]) with mapi; Fri, 1 Oct 2010 13:59:20 -0400 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: binary From: Ken Leach <ktl@KTLGroupInc.com> To: Dave EDI <IMCEAEX-_o=CrimzonRose_ou=First+20Administrative+20Group_cn=Recipients_cn=csouza@crimzonrose.com> This part does not make sense.. it is mapping DAVE EDI (old user on old server) to a new user!? and not even the one I sent the invite to? I sent the request to MCzajkowski@crimzonrose.com not csouza or dave edi!!!???? Subject: fake meeting please ignore Thread-Topic: fake meeting please ignore Thread-Index: Acthkdt3RMHScPJwRB+yUgOaaLziVgAAITXw Date: Fri, 1 Oct 2010 17:59:23 +0000 Content-Language: en-US X-MS-Has-Attach: X-Loop: MCzajkowski@crimzonrose.com X-MS-TNEF-Correlator: dcb855bf-1e81-429d-9d51-c4ad3a5905d8 authentication-results: cm-omr6 smtp.user=ktl@ktlgroupinc.com; auth=pass (LOGIN) x-authenticated-uid: ktl@ktlgroupinc.com x-mailer: Microsoft Office Outlook 12.0 received-spf: None (EXCHANGE2010.crimzonrose.domain: ktl@KTLGroupInc.com does not designate permitted sender hosts) MIME-Version: 1.0 Message-ID: <e2157363ea13417b84e0fb1eb83fab38@EXCHANGE2010.crimzonrose.domain
October 1st, 2010 2:29pm

Check your Outlook nic cache and contacts to make sure you don't have the old address somewhere. But if you are inviting user A and getting an NDR from user B (on an old server) it may be that there is stale delegate information in the invite. If you check with the intended recipient did they receive the invite? Do others sending an invite to the same user experience the same issue (if so that would lend itself to a delegate issue most likely). Chris
Free Windows Admin Tool Kit Click here and download it now
October 1st, 2010 2:46pm

We have tried to send and invite from multiple users internally and externally.. everyone gets the same bounce.. The new user can get all email fine.. just meeting requests seems to have an issue.. -Ken
October 1st, 2010 2:50pm

I'm having the same trouble. Send a calendar invite to person A and get a bounce back saying mail could not be delivered to person B. (I tried a fresh install of outlook, sending from OWA, etc.) - I'm not the only person who gets the delivery failure, anyone in our organization who tries to send person A a calendar invite gets the bounce back. I have confirmed that person A is in fact receiving the invite.
Free Windows Admin Tool Kit Click here and download it now
October 28th, 2010 6:34pm

It sounds like an orphan delegate. Check the user's calendar and see if they haven't delegated permission to a user that's no longer there.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "
October 28th, 2010 7:27pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics