3.1.4.8.4 Sending a Meeting Response

After choosing a response, an attendee or a delegate of the attendee sends a Meeting Response object to inform the organizer of the attendee's choice. The client SHOULD NOT send a Meeting Response object if one of the following conditions is true:

• The attendee is also the meeting organizer.<67>

• The value of the PidTagResponseRequested property ([MS-OXOMSG] section 2.2.1.46) on the Meeting Request object is set to FALSE. (An example of why this property might be set to FALSE is the case in which a very large number of attendees are invited to a meeting and the organizer does not want her Inbox folder flooded with replies.)

If the following condition is true, the client can require sending a Meeting Response object to the organizer:

• The auxApptFlagForceMtgResponse bit is set on the PidLidAppointmentAuxiliaryFlags property (section 2.2.1.3) of the Meeting object (which came from the Meeting Request object or Meeting Update object).

Beyond these constraints, the client can send a Meeting Response object to the organizer to inform the organizer of the attendee's choice. To do so, the client creates and submits a new Meeting Response object. The client then copies the following properties from the Meeting object to the Meeting Response object:<68>

• PidLidLocation (section 2.2.1.4)

• PidLidWhere (section 2.2.5.3)

• PidLidAppointmentSequence (section 2.2.1.1)

• PidLidOwnerCriticalChange (section 2.2.1.34)

• PidTagStartDate (section 2.2.1.30)

• PidTagEndDate (section 2.2.1.31)

• PidLidAppointmentStartWhole (section 2.2.1.5)

• PidLidAppointmentEndWhole (section 2.2.1.6)

• PidLidGlobalObjectId (section 2.2.1.27)

• PidLidIsException (section 2.2.1.35)

• PidTagOwnerAppointmentId (section 2.2.1.29)

• PidTagSensitivity ([MS-OXCMSG] section 2.2.1.13)

In addition to these properties, if the Meeting Response object represents a recurring series, the client MUST copy the following properties from the Meeting object:<69>

• PidLidTimeZoneStruct (section 2.2.1.39)

• PidLidAppointmentRecur (section 2.2.1.44)

• PidLidAppointmentTimeZoneDefinitionRecur (section 2.2.1.41)

• PidLidIsRecurring (section 2.2.1.13)

• PidLidTimeZone (section 2.2.5.6)

• PidLidTimeZoneDescription (section 2.2.1.40)

The client MUST also set the following on the Meeting Response object:

• The value of the PidTagMessageClass property ([MS-OXCMSG] section 2.2.1.3) as specified in section 2.2.7.1.

• The value of the PidTagIconIndex property as specified in section 2.2.1.49.

• The value of the PidLidAttendeeCriticalChange property (section 2.2.5.2) to the current date and time.

• The value of the PidTagSubjectPrefix property ([MS-OXCMSG] section 2.2.1.9) to indicate the response type.

• Increment the value of the PidTagConversationIndex property, as specified in [MS-OXOMSG] section 2.2.1.3.

• The value of the PidTagSentRepresentingName property ([MS-OXOMSG] section 2.2.1.57) to the value of the PidTagMailboxOwnerName property ([MS-OXCSTOR] section 2.2.2.1) from the user's mailbox (for example, a delegate acting on behalf of the delegator would write the name of the delegate).

• The value of the PidTagSentRepresentingEntryId property ([MS-OXOMSG] section 2.2.1.56) to the value of the PidTagMailboxOwnerEntryId property ([MS-OXCSTOR] section 2.2.2.1) from the user's mailbox.

• The value of the PidLidIsSilent property (section 2.2.7.7) to TRUE if the user did not write any text in the body of the response.