PRB: Simple MAPI Application Seems to Ignore Custom Security Settings (826557)


The information in this article applies to:

  • Microsoft Outlook 2000
  • Microsoft Outlook 2002

SYMPTOMS

Custom applications that use Simple MAPI to automate e-mail tasks are subject to the Outlook Security Update. Typically, the custom application prompts the user to permit automatic sending of e-mail messages or to grant access to the Address book. In Microsoft Exchange Server environments, an Exchange administrator can override the default behavior by modifying the Outlook Security Update settings. In some situations, the custom application seems to ignore the custom settings. This problem may be intermittent or consistent.

CAUSE

This problem may occur for many reasons, including the following reasons:
  • The Outlook Security Settings public folder is not correctly named. The public folder that contains the custom security settings must be named exactly as instructed in the Readme file that is included with the Outlook Security Features Administrative Package. For Outlook 2000, the name must be Outlook Security Settings. For Outlook 2002, the name can be either Outlook Security Settings or Outlook 10 Security Settings, depending on the settings in the CheckAdminSettings registry key. For more information, see the Readme file.
  • Outlook is configured to deliver to a personal folders (.pst) file. If the Outlook profile that you are using is configured to deliver locally to a .pst file, the Outlook security settings are not read and the custom application reverts to the default security settings.
  • The Outlook Security Settings public folder does not have the correct security settings. The domain user account that the custom application runs under must be able to read items in the Outlook Security Settings public folder.
  • The Exchange Server computer that hosts the Outlook Security Settings public folder is not available. If the public folder is not available for any reason, including a network outage or an Exchange Server computer outage, the custom application reverts to the default security settings.
  • The computer that hosts the custom application does not have the correct registry settings. For custom applications to comply with the custom security settings, Outlook must be configured to look for custom settings by using the instructions that are included in the Outlook Security Features Administrative package.

RESOLUTION

To resolve this problem, follow these steps:
  1. Verify that the computer that hosts the custom application has the correct registry keys. The registry key can be found in the following location:

    HKEY_CURRENT_USER\Software\Policies\Microsoft\Security\CheckAdminSettings

    Note For more information, see the Readme file that is included with the Outlook Security Features Administrative package.
  2. Make sure that the Outlook Security Settings public folder is available.
  3. Make sure that you can browse the public folder tree to the Outlook Security Settings public folder and view the contents of the folder.
  4. Verify that the Outlook Security Settings public folder is named correctly.

STATUS

This behavior is by design.

MORE INFORMATION

For more information about Outlook security features, click the following article numbers to view the articles in the Microsoft Knowledge Base:

290500 Description of the developer-related e-mail security features in Outlook 2002

290499 OL2002: Administrator Information About E-Mail Security Features

262701 OL2000: Developer Information About the Outlook E-mail Security Update

263297 OL2000: Administrator Information About the Outlook E-mail Security Update

Modification Type:MinorLast Reviewed:3/15/2006
Keywords:kbprb kbMsg KB826557 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.