Outlook Security Manager is a programming tool to control Outlook Security effectively from inside of the Outlook add-ins and applications that interact with Outlook. Supports .NET, VCL and ActiveX platforms, allows you to avoid security warnings and makes possible the use of all Outlook objects without such interference.
Vendor
MAPILab
Company Website
MAPILab Ltd, together with Add-in Express Ltd., have released Outlook Security Manager (.NET, VCL and ActiveX editions). Outlook Security Manager is a programming tool designed to control Outlook Security effectively from inside of Outlook add-ins and applications that interact with Outlook. Outlook Security Manager supports .NET, VCL and ActiveX platforms, allows you to avoid security warnings and makes it possible to use all Outlook objects without having to deal with a host of warnings. This tool supports all Outlook versions starting from Outlook 2000 and provides the easiest way to get round Outlook Security while getting on with Outlook Object Model (OOM), Collaboration Data Objects (CDO) and Simple MAPI (SMAPI).
How it works
If you are going to develop Outlook add-ins or applications that interact with Outlook, you will run into or have already run into Outlook Security. Key Outlook objects such as the address book or mail items including their properties and methods are protected by Microsoft Outlook E-mail Security. Calling this aspect of Outlook inevitably induces the appearance of warning messages. Outlook Security Manager is an in-process COM object that handles all the internal security events of Outlook. Outlook Security Manager is developed as a wrapper covering the COM object which directly supports the three platforms, .NET, VCL and ActiveX, whilst taking into account a platform's peculiarities. Please note all of the editions are included within one licensed package. Unlike some similar tools, Outlook Security Manager doesn't transform OOM and CDO calls to Extended MAPI calls and doesn't make the development more complicated with its own special objects. It just implements one object with three properties that enables or disables Outlook Security for OOM, CDO and SMAPI. These properties are DisableOOMWarnings, DisableCDOWarnings and DisableSMAPIWarnings. Before calling a protected object you just disable Outlook Security with the corresponding property, and then turn it on again afterwards.