|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|
PidTagReceivedRepresentingName 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 display name for the messaging user who is represented by the receiving user.
PR_RCVD_REPRESENTING_NAME, PR_RCVD_REPRESENTING_NAME_A, PR_RCVD_REPRESENTING_NAME_W
These properties are examples of the address properties for the messaging user who is being represented by the receiving user. They 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, these properties should be set to the display name contained in the PR_RECEIVED_BY_NAME (PidTagReceivedByName) property.
A client application replying to a message received on behalf of another client should copy these properties from the received message into the PR_SENT_REPRESENTING_NAME (PidTagSentRepresentingName) property for the reply.