Share via

2.1.3.1.2 Reply-To

  • Article

To generate a Reply-To header, clients set the values of the PidTagReplyRecipientEntries property ([MS-OXOMSG] section 2.2.1.43) and the PidTagReplyRecipientNames property ([MS-OXOMSG] section 2.2.1.44).

When generating a MIME message, MIME writers generate a Reply-To header by using the PidTagReplyRecipientEntries and the PidTagReplyRecipientNames properties. MIME writers SHOULD ignore the value of the PidTagReplyRecipientNames property if the count of names does not match the count of entries in the PidTagReplyRecipientEntries property. Assuming the counts do match, each entry in the value of the PidTagReplyRecipientNames property maps to one display name, and each EntryID in the value of the PidTagReplyRecipientEntries property maps to one address, as follows:

  1. If bytes 4-19 are equal to the MUIDEMSAB UUID value "{%xdc.a7.40.c8.c0.42.10.1a.b4.b9.08.00.2b.2f.e1.82}", it is an address book EntryID. (The MUIDEMSAB value identifies the value as an EntryID.) In this case, the MIME writer SHOULD look up the address book entry that corresponds to the DN that is contained in the EntryID, and use its primary SMTP proxy address.

  2. If bytes 4-19 are equal to the MUIDOOP UUID value "{%x81.2b.1f.a4.be.a3.10.19.9d.6e.00.dd.01.0f.54.02}", it is a one-off EntryID. The e-mail type and address are encoded in the one-off EntryID, as specified in [MS-OXCDATA] section 2.2.5.1, and SHOULD be extracted. If the e-mail type is SMTP, the e-mail address SHOULD be used as is; otherwise, the address MUST be IMCEA-encapsulated, as specified in section 2.1.3.1.8.

When generating a TNEF message, MIME writers SHOULD<12> also copy the values of the PidTagReplyRecipientEntries and the PidTagReplyRecipientNames properties to the attMsgProps attribute, as specified in [MS-OXTNEF] section 2.1.3.3.21, in the TNEF body part.