Hello, I have a customer that is running Exchange 2003, with Outlook 2010. I am not sure this has anything to do with a specific version of Exchange or Outlook. My customer has customers that are able to send them a Calendar Request. It appears that it is a valid person that they know, and that they are from outside of their organization. The people are able to send them calendar requests that are mandatory, and they show up on their calendar as mandatory, and they do not get the Accept, Decline, etc. buttons. They want to block anyone from requiring attendance of anyone in their office. Is it possible for anyone outside of their organization to send a calendar item, and require attendance? If so, can they block this from being set as mandatory attendance on their calendar, or at least have the option of deleting it? Thanks

So, it seems that the meeting requests from the external domain have been accepted automatically, right? Does it happen to the meeting requests from all the external domains? Does AAA (Auto Accept Agent) have been deployed on the exchange server? Please check if the issue can be reproduced if the user receives the request via OWA when the outlook has been closed James Luo TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com 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.

Yes, these are meeting requests from external domains. No, and as far as I can tell, not all meeting requests. No Auto-Accept Agent has been deployed on the server to the best of my knowledge. Is there a way I can check? I will check to see if the issue can be reproduced under those circumstances. Thanks, Terrill

Any further update about the case?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.

Sorry about the delay. After testing with Microsoft Technical Support, we could no longer replicate the problem. All we could come up with is there was an update that fixed the problem. Thanks!