Outlook 2003 non-invited attendee's receiving meeting invites

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have user A, B, and C. A is the intended Receiver of the invites. User A
which is receiving invites through Outlook 2003. When you send user A an
invite user B and user C receive the same invite which was not intended for
them. I've checked all permissions and delegates and they have no connection
what so ever. User B has access to user A's inbox and has never been a
delegate on user A's machine. I removed user B's permissions to access user
A's Inbox. And still the same problem. User C has never had any connection
with any of the users. Could this be a connection between a deleted account
or a group of some sort in exchange or AD. I'm not sure what else to do I
have been working on this for way to long and need a resolution for this once
and for all. Any help would be appriciated.
 
Sounds like the hidden delegate rule still might be forwarding those requests. You can delete the delegate rule with the free MAPI Editor tool from http://www.microsoft.com/downloads/details.aspx?familyid=55FDFFD7-1878-4637-9808-1E21ABB3AE37. Complete instructions in the mfcmapi.doc included with the download.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
 
Is there anyway else I can change this Hidden Delegate? Do you know of
another way or some other tutorial that might help? I'm not familiar with
MAPI. If I was to approach this through MAPI can this be done on a users
machine, and will the affects be Globally or just locally?
 
Was there something you didn't understand about my earlier post, which pointed you toward the solution?

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
 
Sue Mosher said:
Was there something you didn't understand about my earlier post, which pointed you toward the solution?

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
 
The symptoms certainly suggest that there is something wrong with the mailbox itself. You could try the alternative Outlook Spy tool (http://www.dimastr.com) to see if it can work around the possible corruption. If that doesn't work, you might ask for other ideas in the microsoft.public.exchange.clients forum before giving up and rebuilding the mailbox.
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
 
Back
Top