|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here. ArchiveDisclaimer|
PidTagReceivedRepresentingSearchKey Canonical Property
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
Contains the search key for the messaging user represented by the receiving user.
This property is one of the address properties for the messaging user being represented by the receiving user. It must be set by the incoming transport provider, which is also responsible for authorization or verification of the delegate. If no messaging user is being represented, this property should be set to the search key contained in the PR_RECEIVED_BY_SEARCH_KEY (PidTagReceivedBySearchKey) property.
A client application replying to a message received on behalf of another client should copy this property from the received message into the PR_SENT_REPRESENTING_SEARCH_KEY (PidTagSentRepresentingSearchKey) property for the reply.