2.2.5.1.2.2 OP_REPLY and OP_OOF_REPLY ActionData Structure
The ActionData structure used in an action (2) of type "OP_REPLY" or "OP_OOF_REPLY" is one of two formats, depending on whether the rule (2) is a standard rule or an extended rule. Prior to creating a rule (2) that has an action (2) of "OP_REPLY" or "OP_OOF_REPLY", the client is required to first create an FAI message to be used as the reply template. For details about creating a reply template, see section 3.1.4.2.5.
Buffer Format for Standard Rules
The OP_REPLY and OP_OOF_REPLY ActionData structure MUST be in the following format for a standard rule.
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
ReplyTemplateFID |
|||||||||||||||||||||||||||||||
|
... |
|||||||||||||||||||||||||||||||
|
ReplyTemplateMID |
|||||||||||||||||||||||||||||||
|
... |
|||||||||||||||||||||||||||||||
|
ReplyTemplateGUID (16 bytes) |
|||||||||||||||||||||||||||||||
|
... |
|||||||||||||||||||||||||||||||
|
... |
|||||||||||||||||||||||||||||||
ReplyTemplateFID (8 bytes): A Folder ID structure, as specified in [MS-OXCDATA] section 2.2.1.1, that identifies the folder that contains the reply template.
ReplyTemplateMID (8 bytes): A Message ID structure, as specified in [MS-OXCDATA] section 2.2.1.2, that identifies the FAI message being used as the reply template.
ReplyTemplateGUID (16 bytes): A GUID that is generated by the client in the process of creating a reply template. The value of the ReplyTemplateGUID field is equal to the value of the PidTagReplyTemplateId property (section 2.2.9.2) that is set on the reply template.
Buffer Format for Extended Rules
The OP_REPLY and OP_OOF_REPLY ActionData structure MUST be in the following format for an extended rule.
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
MessageEIDSize |
|||||||||||||||||||||||||||||||
|
ReplyTemplateMessageEID (70 bytes) |
|||||||||||||||||||||||||||||||
|
... |
|||||||||||||||||||||||||||||||
|
... |
|||||||||||||||||||||||||||||||
|
ReplyTemplateGUID (16 bytes) |
|||||||||||||||||||||||||||||||
|
... |
|||||||||||||||||||||||||||||||
|
... |
|||||||||||||||||||||||||||||||
MessageEIDSize (4 bytes): An integer that specifies the size, in bytes, of the ReplyTemplateMessageEID field.
ReplyTemplateMessageEID (70 bytes): A Message EntryID structure, as specified in [MS-OXCDATA] section 2.2.4.2, that contains the entry ID of the reply template.
ReplyTemplateGUID (16 bytes): A GUID that is generated by the client in the process of creating a reply template. The value of the ReplyTemplateGUID field is equal to the value of the PidTagReplyTemplateId property that is set on the reply template.