Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
5.1 Security Considerations for Implementers
Collapse the table of content
Expand the table of content

5.1 Security Considerations for Implementers

When the message is delivered, the presence of the PidNamePhishingStamp property ([MS-OXPROPS] section 2.461) with a successful match of the STAMP field, as specified in section, signals the client that the message has already been evaluated for phishing and does not have to be filtered again. Therefore, care has to be taken while setting the PidNamePhishingStamp property on the message, and all precautions for evaluation of the fifth value of PidTagAdditionalRenEntryIds ([MS-OXPROPS] section 2.500) have to be followed (as described in [MS-OXCMSG]).

© 2015 Microsoft