3.1.5.6.1 Substitute Meeting Invitation Email
To send a substitute meeting invitation email message, the server creates a temporary item. The server MUST NOT modify or remove the original meeting request in order to create the temporary item.
The substitute meeting invitation email message elements are set according to the following table.
|
Substitute meeting invitation email message element |
Value |
|---|---|
|
email:To |
Set to the email address of the delegate. |
|
email:Cc |
Blank. |
|
email:From |
Copy value from original meeting request. |
|
email:Subject |
Original subject prepended with explanatory text. |
|
email:DateReceived |
Copy value from original meeting request. |
|
email:DisplayTo |
Copy value from original meeting request. |
|
email:ThreadTopic |
Copy value from original meeting request. |
|
email:Importance |
Copy value from original meeting request. |
|
email:Read |
Copy value from original meeting request. |
|
airsyncbase:Body |
Summary of meeting details. |
|
email:MessageClass |
Set to "IPM.Note". |
|
email:InternetCPID |
Copy value from original meeting request. |
|
email:Flag |
Copy value from original meeting request. |
|
email:ContentClass |
Set to "urn:content-classes:message". |
|
airsyncbase:NativeBodyType |
Copy value from original meeting request. |
|
email2:ConversationId |
Copy value from original meeting request. |
|
email2:ConversationIndex |
Copy value from original meeting request. |
|
email:Categories |
Copy value from original meeting request. |
The exact format of the explanatory text for the email:Subject element is implementation-specific but SHOULD indicate that the email message represents a meeting request for the delegator.
The exact format of the airsyncbase:Body element is implementation-specific but SHOULD include summary details of the original meeting request, such as date, time, and location.
Actions taken by the client on the substitute meeting invitation email message will actually take effect on the original meeting request on the server (for example, flagging the substitute meeting invitation email message for follow-up will result in the original meeting request being flagged for follow-up on the server), with the following exceptions:
Replying to the substitute meeting invitation email message with the SendMail command will reply to the substitute meeting invitation email message. The server will append the original meeting request to the reply.
Forwarding the substitute meeting invitation email message with the SendMail command will forward the substitute meeting invitation email message. The server will append the original meeting request to the forwarded message.
Any attachments on the original meeting request are not exposed via the substitute meeting invitation email message.
For an example of a substitute meeting invitation email message, see section 4.5.11.