Outlook Redemption

How Outlook Redemption works

Redemption is a regular COM library; once registered on the system, it is accessible to any programming language (VB, VBA, VC++, Delphi, etc). Redemption uses Extended MAPI (which is not affected by the Security Patch since it is not accessible to the scripting languages) to duplicate the functionality blocked by the Security Patch.

All Safe item Redemption objects have an Item property which must be set to an Outlook item. Once set, you can access any properties and methods, both blocked and not blocked.

For the blocked properties and functions, Redemption objects completely bypass the Outlook object model and behave exactly like Outlook objects with no Security Patch applied.

For the properties and methods not blocked by the Security Patch, all calls are transparently forwarded to the Outlook object that you assign to the Item property. With this approach changes to your code are minimal: you only change the way you declare the objects, but not the rest of your code that actually accesses both blocked and not blocked properties and methods.

Using Outlook Redemption

Redemption objects providing access to the properties, functions and objects blocked by the Outlook Security Patch. In addition to providing the exact replica of the corresponding Outlook objects, some of these objects have extra properties and methods, such as RTFBody on all Safe Item objects, AsString and AsArray on attachments, etc. These objects are designed to be used alongside your existing OOM or CDO 1.21 code with as few modifications as possible.

RDO (Redemption Data Objects) library is designed to be used as a complete CDO 1.21 replacement. This family of objects is designed to be used standalone, but it can of course still be used along with your existing OOM or CDO code.

Miscellaneous Redemption objects providing access to the Extended MAPI properties and functionality not available through the Outlook Object Model.