RESOLUTION
To resolve this problem, you must do both of the following:
- You must obtain and install the hotfix that is described in
this article.
-and- - You must expose the named property in your custom message
store.
How to Obtain the Hotfix
This issue is fixed in the Microsoft Outlook 2002 Post-Service
Pack 2 Hotfix Package August 10, 2003. For additional information, click the
following article number to view the article in the Microsoft Knowledge Base:
823970 Availability of the Outlook 2002
Post-Service Pack 2 Hotfix Package: August 10, 2003
How To Expose The Named Property In Your Code
Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements. The property your custom message store must expose
is a named property. The following are the components of the named property:
const GUID PSETID_Common = {0x00062008, 0, 0, {0xC0, 0, 0, 0, 0, 0, 0, 0x46}};
lpguid = PSETID_Common;
ulKind = MNID_STRING;
Kind.lpwstrName = L"ArchiveSourceSupportMask";
The type of the named property is
PT_LONG.
Valid values are a combination of the following flags:
enum
{
ASM_DEFAULT = 0, // Allow archiving
ASM_DO_NOT_ARCHIVE = 1 << 0x0, // Do not allow archiving
ASM_CLIENT_DO_NOT_CHANGE = 1 << 0xF // Do not allow client to set archiving flags
};
Note ASM_CLIENT_DO_NOT_CHANGE is defined for future reference and is
not currently implemented in this fix. For now, a store can prevent clients
from changing these flags by hardcoding the values that the store returns for
the property.