Article ID: 177853
Article Last Modified on 2/19/2007
APPLIES TO
- Microsoft Messaging Application Programming Interface
- Microsoft Exchange Server 5.5 Standard Edition
- Microsoft Exchange 2000 Server Standard Edition
This article was previously published under Q177853
SYMPTOMS
When the PR_SECURITY property is set (either directly through Extended MAPI or indirectly with CDO 1.21's Encrypted or Signed properties), the property has no apparent effect.
CAUSE
The Exchange MAPI providers ignore the PR_SECURITY property. Per MAPI specifications, it is up to the underlying MAPI providers whether or not to honor the PR_SECURITY property, and it is not required.
STATUS
This behavior is by design.
MORE INFORMATION
The Microsoft Developer Network Library (MSDN) topic on PR_SECURITY states the following:
The underlying messaging system chooses whether to use the flag Contained in the PR_SECURITY property.
Additional query words: PR_SECURITY property flag security advanced signed
Keywords: kbapi kbmsg kbprb KB177853
