I think it should be the user's choice to send a response, as designed. There are certainly meeting request scenarios where responding isn't necessary. Note that only such a response can update the meeting for the sender, since the invitees almost certainly do not have permission to write to the item in the meeting organizer's calendar.
I am certainly glad that you decided to post your response to my question.
It wouldn't be too helpful to me if you answered the question and kept it to
yourself which is what your post suggested.
If a user pushes one of the accept, tentative or decline buttons, this
information should be automatically sent. If the user does not want to
respond to the request, they should delete the email. Case in point, I
organize a meeting with you and you accept but do not send me a response. I
look at the meeting request 5 minutes before the meeting, notice that you
have not responded, try to call you but you have left your office and are
coming to the meeting so I decide to not go to my meeting because you didn't
respond to me and you are sitting in the meeting wondering where I am. There
are so many layers of inefficiency built into this "feature".
> I think it should be the user's choice to send a response, as designed. There are certainly meeting request scenarios where responding isn't necessary. Note that only such a response can update the meeting for the sender, since the invitees almost certainly do not have permission to write to the item in the meeting organizer's calendar.
>
[quoted text clipped - 23 lines]
> >
> > http://www.microsoft.com/office/community/en-us/default.mspx?mid=a1139434-afc7-4
556-b062-066b5077604d&dg=microsoft.public.outlook.calendaring
Sue Mosher [MVP-Outlook] - 26 Oct 2005 15:16 GMT
Unfortunately, doing it the way you describe probably would require a complete redesign of the entire Outlook meeting request architecture. As with any system that involves collaboration -- be it electronic or face-to-face -- some degree of training is required to set expectations and share best practices.
Your additional comments, though, do flesh out the scenario better so that Microsoft can consider them for future versions.

Signature
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx
>I am certainly glad that you decided to post your response to my question.
> It wouldn't be too helpful to me if you answered the question and kept it to
[quoted text clipped - 37 lines]
>> >
>> > http://www.microsoft.com/office/community/en-us/default.mspx?mid=a1139434-afc7-4
556-b062-066b5077604d&dg=microsoft.public.outlook.calendaring