Showing posts with label MAPI. Show all posts
Showing posts with label MAPI. Show all posts

Monday, July 30, 2012

Exchange 2013 says "See ya MAPI and goodbye Outlook 2003!" Exchange 2013 drops MAPI support

The Email Admin - Major Changes in Store with Exchange 2013

Microsoft recently announced the Exchange Server 2013 Preview, and admins everywhere should be very excited about the next generation in Exchange technologies. While I am very excited myself about the possibilities, I can foresee a few things about Exchange 2013 that may come as a surprise to many, and might require some others to make a sea change in the way they think, so better to discuss these now.

Bye-bye MAPI

In Exchange 2013, clients can connect using POP3, IMAP, SMTP, and the various HTTPS protocols, including Outlook Anywhere, Exchange ActiveSync, and Exchange Web Services. However, old-school MAPI connections are gone. I’ve worked with a number of customers who have a strange fear of Outlook Anywhere, and this may cause them some heartburn.

...

image..."

Ah, MAPI I knew you well. From your earliest days when you were competing with VIM (Vendor Independent Messaging, put forth by Lotus in the cc:Mail days) through today with the Outlook Connector which put a MAPI face on Hotmail. Still I guess time moves forward, technology changes and needs morph. Still it's a little weird to see you getting the boot...

Monday, April 09, 2012

Improving your Outlook with MFCMAPI (Or Email Admin's Intro to MFCMAPI)

The Email Admin - Troubleshooting Outlook Issues with MFCMAPI

"We’ve been covering a lot of new tools that Microsoft and the Exchange team have been releasing recently. The folks from Redmond have been busier than North Pole elves in December, and we continue to see great things coming down the pipe. But in today’s post, we’re going to take a closer look at a slightly older, but also incredibly powerful tool, called MFCMAPI. In this article, we’ll introduce you to the tool, go over some of its capabilities, and provide you links to resources for further information. If there’s enough interest, we may start a series of how-to’s for using MFCMAPI to troubleshoot a variety of different issues.

MFCMAPI is a free tool available for download from Codeplex at http://mfcmapi.codeplex.com/. It comes in both 32 and 64 bit versions. We indicated that it’s an older tool, but it’s a tool that has been updated regularly since it was released in August 2007, and was updated just last month. MFCMAPI is a GUI tool that can connect to your Exchange mailbox using the same profile and settings as your Outlook client, but rather than acting as a mail client, it functions as a MAPI client. It makes the same connections to Exchange as Outlook does, but shows you what those connections are and allows you to manipulate the objects within your mailbox using MAPI calls, rather than the Outlook interface. This allows you to query, search, delete, and modify objects within your mailbox. Here’s a short list of things you can do with MFCMAPI:

  1. Troubleshoot client connections
  2. Troubleshoot Free/Busy
  3. Delete corrupt email rules
  4. Hide or reveal folders
  5. Delete delegate permissions from a mailbox
  6. Troubleshoot BlackBerry Enterprise Activation
  7. Troubleshoot Out Of Office
  8. Determine what flags a message as junk (antivirus software or Outlook Junk email filter)
  9. Troubleshoot Address Book issues
  10. Troubleshoot profile issues
  11. Troubleshoot Public Folders
  12. Convert between MSG and EML formats

...

image..."

MFCMAPI

MFCMAPI uses Microsoft's published APIs to provide access to MAPI stores through a graphical user interface. Its purpose is to facilitate investigation of Exchange and Outlook issues and to provide developers with a canonical sample for MAPI development.

...

MFCMAPI is a project that I've been following for years now. If you're a hardcode MAPI coder you probably already know about MFCMAPI, but sysadmins/email admins might not. That's what caught my eye in this post, the focus on real world email admins and using it as a real tool...

 

Related Past Post XRef:
November 2011 Update for MFCMAPI and MrMAPI (Think, "MFCMAPI, You're looking kind of Metro" release)
MFCMAPI - Articles-a-pluza!

Microsoft Format and Specification Documentation Refresh ("Significantly changed technical content") [Updated: Includes updates for Office 15 Technical Preview ]

A start in understanding the MS-PST Node Database Layer, your first step toward PST binary enlightenment…
MS-PST file format specification released. Yep, the full and complete specification for Outlook PST’s is now just a download away.
Open source PST SDK/library… from Microsoft!? Yep!

Tuesday, November 29, 2011

November 2011 Update for MFCMAPI and MrMAPI (Think, "MFCMAPI, You're looking kind of Metro" release)

SGriffin's MAPI Internals - November 2011 Release of MFCMAPI and MrMAPI

"The November 2011 Release (build 15.0.0.1029) is live: http://mfcmapi.codeplex.com.

Note that build number. That’s right. I jumped all the way from 6 (where I’ve been stuck forever) to 15. That’s the sort of jump that’s normally only accompanied by a full UI refresh. And that’s exactly what you get! I’ve overhauled just about every aspect of the UI for a more modern, some might say “Metro inspired”, look. I’ll admit, there’s still some work to be done (I didn’t get to scrollbars for instance) but this is a pretty good start. Let’s take a look:

image

I’ve drastically slimmed down the menus, stuffing most of the little used functionality into Advanced menus that most of you will never need to open. The old, usually empty, File menu is gone and Session now takes prominence. This should help new users immensely. Long time users of MFCMAPI may want to spend a little time figuring out where their favorite features went, but nothing’s been cut.

..."

If you do MAPI/Outlook/PST's/EDD/ESI this is one of those must have in your toolbox utilities...

Monday, June 13, 2011

MFCMAPI - Articles-a-pluza!

SGriffin's MAPI Internals - MFCMAPI: Documentation By Committee

I’ve noticed over the years that a number of articles have been written documenting how to use MFCMAPI to troubleshoot various issues. I thought it would be a good idea to put together a list of these articles in one central location. So after much searching with the Bing and with the Google, I’ve put together this list:

…”

CodePlex - MFCMAPI - Articles

SNAGHTML76575915

image…”

If you’ve heard of MFCMAPI then you’ll know why this cool list of related articles is, well, cool! If not, check out the main Project Page and Steven Griffin’s blog 

 

Related Past Post XRef:
A start in understanding the MS-PST Node Database Layer, your first step toward PST binary enlightenment…
[Cool Project to Watch of the Day] PSTSDK.Net, a .NET port of PST File Format SDK
Open source PST SDK/library… from Microsoft!? Yep!

MS-PST file format specification released. Yep, the full and complete specification for Outlook PST’s is now just a download away.
PST File Format Documentation coming…

I'll Need This Later Note To Self: .Net and MAPI/CDO Don't Mix
VB.NET DLL Wrapper For C MAPIEx Extended MAPI

Tuesday, November 30, 2010

A start in understanding the MS-PST Node Database Layer, your first step toward PST binary enlightenment…

Microsoft Open Specification Support Team Blog - MS-PST - How to Navigate the Node BTree

“The current version of the MS-PST open specification document can be found here: http://msdn.microsoft.com/en-us/library/ff385210(office.12).aspx

Introduction

The PST is a structured binary file format that contains messages, folders, and attachments. The file structure can be logically separated into 3 layers: the Node Database (NBD) layer, the Lists, Tables, and Properties (LTP) layer, and the Messaging layer. Each layer builds on the one before and because of this it is necessary to completely understand the NDB layer before the LTP layer, and to understand the LTP layer before the Messaging layer. Like building a house, you cannot start framing the walls until you pour the foundation. The Node BTree, which is an important part of the NBD layer is part of that foundation. Without it, you could not hope to be able to understand how the PST file format works much less be able to find what you are looking for.

We will be focusing on the Unicode version of the PST file format that was introduced in Outlook 2003 since most of the PST files you are likely to be working with will be in this format. Information on the differences between the Unicode and ANSI version can be found in section 2.2.1.2.

pagesnap…”

I love this kind of documentation. Understand binary formats are hard enough (I’ve been living in MS-CFB, MS-OLEPS, MS-OLSDS, MS-DOC and MS-XLS recently and let me tell you, my brain really hurts… ;) so this kind of walk through helps a great deal (Pictures = Less Greg Brain Pain ;). Sure it’s just barely scratching the surface, but sometimes all you need is a slight boost to get you going…

 

Related Past Post XRef:
MS-PST file format specification released. Yep, the full and complete specification for Outlook PST’s is now just a download away.
Open source PST SDK/library… from Microsoft!? Yep!

The Microsoft Office Visualization Tool (OffVis) – Spelunk (view, browse, peek into, etc) Microsoft Office Binary Format files
Microsoft Office (DOC, XLS, PPT) Binary File Format Specifications Released – We’re talking the full technical specification… (The [MS-DOC].pdf alone is 553 pages of very dense specification information)
DOC, XLS and PPT Binary File Format Specifications Released (plus WMF, Windows Compound File [aka OLE 2.0 Structured Storage] and Ink Serialized Format Specifications and Translator to XML news)
Microsoft Office Binary File Format Specifications Coming to a Download Near You...

Thursday, May 27, 2010

[Cool Project to Watch of the Day] PSTSDK.Net, a .NET port of PST File Format SDK

When Microsoft released the PST SDK (post), my first thought was “Oh I SO want a Managed/.Net wrapper/port!” It’s pretty obvious I wasn’t the only one with this wish (“Gee no kidding Caption Obvious?” LOL)…

Troy dropped me a comment to let me know he was already on it.

CodePlex - pstsdk.net: .NET port of PST File Format SDK

Project Description
pstsdk.net makes it easier for .NET developers to access the PST file format. This is a direct C# port of the PST File Format SDK project which is written in C++.

Current Status
Just getting started. So far primitives.cs is the only file with any content. More to come...”

Added to my watch list. Again, thanks for the heads up Troy!

 

Related Past Post XRef:
Open source PST SDK/library… from Microsoft!? Yep!

Monday, May 24, 2010

Open source PST SDK/library… from Microsoft!? Yep!

Microsoft PressPass - Microsoft Delivers on Interoperability Principles With Office Outlook

REDMOND, Wash. — May 24, 2010 — Microsoft Corp. today announced the availability of two new open source projects that complement technical documentation recently released for Microsoft Outlook Personal Folders (.pst). Combined, the documentation and tools advance interoperability with data stored in .pst files, reflecting customer requests for greater access to data stored and shared in digital formats generated by Microsoft Outlook and for enhanced data portability.

Developers can use these resources to more easily build solutions, including competitive products, that run on top of the .pst file format, unlocking data stored in .pst files in simple scenarios, such as extracting photos stored in .pst files to create an album, as well as more complex scenarios, including archive search, e-discovery and corporate compliance, and uploading data to the cloud.

Now, two new open source projects, a .pst Data Structure View Tool and a .pst File Format Software Development Kit (SDK), further reduce the complexity of reading and extracting data stored in .pst files for use in new applications across a range of platforms. The .pst Data Structure View Tool is a graphical browser of internal data structures for .pst files that enables a developer to better understand .pst file content. The .pst File Format SDK is a cross-platform library that allows developers to read data stored in .pst files and develop applications accessing the data. In the near future, the capability to write data to .pst files will be added to the SDK.

…”

Interoperability @ Microsoft - Two open source projects to facilitate interoperability with Outlook .pst data files

Microsoft today announced the availability of two new open source projects that complement technical documentation recently released for Microsoft Outlook Personal Folders (.pst). From the press release:

Combined, the documentation and tools advance interoperability with data stored in .pst files, reflecting customer requests for greater access to data stored and shared in digital formats generated by Microsoft Outlook and for enhanced data portability.”

The two open source projects, available on Copeplex under the Apache 2.0 license are the following:

  • The PST Data Structure View Tool (http://pstviewtool.codeplex.com/) is a graphical tool allowing the developers to browse the internal data structures of a PST file. The primary goal of this tool is to assist people who are learning .pst format and help them to better understand the documentation.
  • The PST File Format SDK (http://pstsdk.codeplex.com/) is a cross platform C++ library for reading .pst files that can be incorporated into solutions that run on top of the .pst file format. The capability to write data to .pst files is part of the roadmap will be added to the SDK.

To get more details about how these two projects came to life and understand what type of scenarios they enable, watch this video with Daniel Ko, development manager in the Outlook team.

image

…”

CodePlex - PST Data Structure View Tool

“PST Data Structure View Tool (PSTViewTool) is a tool supporting the PST file format documentation effort. It allows the user to browse the internal structures of a PST file.

PSTViewTool is a MFC/C++ app developed in Visual Studio. Other than MFC, it has no external dependencies.

PSTViewTool is largely complete with respect to its goals, and it is no longer actively being enhanced. However, patches and bug reports are welcome.

For reusable code, you should refer to the PST File Format SDK: http://pstsdk.codeplex.com/

CodePlex - PST File Format SDK

“PST File Format SDK (pstsdk) is a cross platform header only C++ library for reading PST files.

Quick Start Guide For Developers (for developers working on PST File Format SDK)
Quick Start Guide For Users (for developers using PST File Format SDK in other projects)

…”

PST File Format SDK - Quick Start Guide For Users

“Using PST File Format SDK in your project is extremely simple.

  1. Unzip PST File Format SDK into a directory of your choosing (e.g, C:\libraries\pstsdk)
  2. Unzip Boost v1.42 into a directory of your choosing (e.g, C:\libraries\boost)
  3. Make sure the PST File Format SDK directory is in your compilers include path
  4. Make sure the Boost directory is in your compilers include path


See the Documentation page for a quick start guide.

Take a look at pstsdk/doc/html/index.html for an in depth API Reference.

Try to read [MS-PST], the published file format documentation on the PST, if you're doing any serious work. It's also included in pstsdk/doc - I included it because various structures in the SDK are annotated with the section of MS-PST they describe/implement; and such sections numbers are likely to change in the future as the document is updated. The version of the document distributed with PST File Format SDK may be out of date, but the section numbers in it will correspond to the sections the API reference links to.

…”

Most of you probably won’t care about this, but I think this is awesome!

I can’t wait to see some of the stuff that’s going to come from the development community because of this (I’ll be keeping my eyes wide open for a Managed wrapper/implementation).

For my current field (i.e. Litigation support, electronic data discovery [EDD], Electronically stored information [ESI], etc) this could be huge. The MS-PST Doc was one thing, this is a whole other ball of wax.

 

Related Past Post XRef:
MS-PST file format specification released. Yep, the full and complete specification for Outlook PST’s is now just a download away.
PST File Format Documentation coming…

Outlook Redemption 4 Released

I'll Need This Later Note To Self: .Net and MAPI/CDO Don't Mix
VB.NET DLL Wrapper For C MAPIEx Extended MAPI

The Microsoft Office Visualization Tool (OffVis) – Spelunk (view, browse, peek into, etc) Microsoft Office Binary Format files
Microsoft Office (DOC, XLS, PPT) Binary File Format Specifications Released – We’re talking the full technical specification… (The [MS-DOC].pdf alone is 553 pages of very dense specification information)
DOC, XLS and PPT Binary File Format Specifications Released (plus WMF, Windows Compound File [aka OLE 2.0 Structured Storage] and Ink Serialized Format Specifications and Translator to XML news)
Microsoft Office Binary File Format Specifications Coming to a Download Near You...

Monday, February 01, 2010

Outlook Spy 2.15 is Outlook 2010 (32bit) compatible

Exchangepedia Blog - Outlook Spy 2.15 is Outlook 2010-compatible

“Didn't notice earlier— one of my favorite Outlook/Exchange tools is now compatible with Outlook 2010. Outlook Spy is primarily a tool for Outlook/Exchange developers, but Exchange administrators also find it useful. It allows you to look under the hood of mailboxes and messages. Created by Dmitry Streblechenko, an Outlook MVP, Outlook Spy has been on my list of "must have Exchange tools" for as long as I can remember. Released in November 2009, the latest version of Outlook Spy (v2.15) adds Outlook 2010 compatibility.

…”

Outlook Spy

“OutlookSpy 2.15

ou_toolbar

OutlookSpy is the ultimate Outlook developer tool. Integrated directly into Outlook, it provides fast and convenient access to all Outlook Object Model objects, lets you examine values of the properties, call functions, browse object hierarchy and monitor Outlook events. CDO is supported too!

If you are a die-hard Extended MAPI developer or just curious about what really goes on under the hood, OutlookSpy will provide you with an access to the Extended MAPI interfaces that Outlook uses internally. See how Outlook data is stored, browse MAPI hierarchy, watch Extended MAPI notifications, or just satisfy your curiosity.

Forget about MdbView, see what you've been missing!

…”

History

“…

11/21/2009 OutlookSpy version 2.15 build 2.15.0.453

  • Added support for Outlook 2010 (32 bit only).
  • More symbolic property tags
  • OutlookSpy now requests PT_UNICODE properties rather than P_STRING8 by default if the object supports Unicode
  • Named MAPI properties with Unicode names (MNID_STRING) were being displayed as ANSI strings.
  • Numerous performance and stability fixes.

…”

I usually don’t blog about closed source and/or pay packages, but I’m gladly making an exception in this case. I’ve been using Outlook Spy (and Office Spy and Redemption) for years and must say it is a must have utility for any Outlook/MAPI developer. This utility has saved my sanity more time than it’s possible for me to count. That and the fact that Dmitry provides outstanding support and is very active in the community (you’ll see him appear in many MAPI/EMAPI/Outlook dev forums) is all icing on the cake.

Now this isn’t a general user utility, but nearly Outlook/MAPI/EMAIP developer will feel right at home with it and learn to quickly love and rely on it…

 

Related Past Post XRef:
I'll Need This Later Note To Self: .Net and MAPI/CDO Don't Mix
Outlook Redemption 4 Released

Monday, November 10, 2008

Save yourself from a “Big R” CLM (Career Limiting Move) – Reply All Information and Confirmation Outlook Macro

Confessions of a Microsoft Consultant - Job/Life/Reputation protector 2.0

“Back in January I posted some simple VBA code for adding an “are you sure?” type question to the Reply To All button in Outlook.  Since then I have received a few suggestions for improving the code, one of the most common of which was to add to the question box the list of names that the mail will be sent to.  So, as requested, you can find below the updated code! 

image_6

Just place this code in a module in Outlook (you can get to the VBA editor by pressing ALT+F11) and then assign it a button on the toolbar

…”

Disabling Reply All can be overkill, but sometimes you also want to sanity check your Reply All too. This little macro/VBA snip can help you with that.

Mix this with a delay sending rule (Outlook's 1-Minute Rule [Auto Defer Email Send for 1 Minute Rule]) and you may save yourself a little future hassle.

 

For more information on “Big R” please see the The Microsoft Lexicon,

Saturday, January 26, 2008

Microsoft Office Outlook 2007 Auxiliary Reference Download

Microsoft Downloads - Microsoft Office Outlook 2007 Auxiliary Reference

"...

The Microsoft Office Outlook 2007 Auxiliary Reference contains conceptual content, reference documentation for twelve sets of APIs, code samples, and a redistributable installer, which allow developers to extend and integrate with Microsoft Office Outlook 2007. This documentation contains conceptual and reference materials for the following:

  • Account Management API
  • Attachment Security API
  • Data Degradation Layer API
  • Free/Busy API
  • Mail Envelope API
  • MAPI-MIME Conversion API
  • Offline State API
  • Outlook Exported APIs
  • Replication API
  • Store API
  • MAPI additions
  • Named properties used by Outlook

In addition, it contains sample tasks and descriptions of four sample projects. For more information about the accompanying samples, see the Outlook 2007 Auxiliary Reference Code Samples and Redistributable Installer.

..."

This is one of those downloads I KNOW I'll need at some future date, but would forget what it's called...

Friday, October 05, 2007

I'll Need This Later Note To Self: .Net and MAPI/CDO Don't Mix

mstehle: The CDOs and CDONTS of Messaging Development - FYI: Why are MAPI and CDO 1.21 not supported in managed (.NET) code?

"The issue of using MAPI or (most commonly) CDO 1.21 in managed (.NET) code is one that comes back to us a lot on the Messaging Developer Support team. Both the messaging technologies in question and the .NET framework have been around for many years at this point. As well have the KB articles that state the supportability [GD: i.e. that MS doesn't support Managed usage of MAPI/CDO1.21] of Outlook and Exchange APIs in managed code. There are three main contributors to steady stream of cases we see – even today – where customers are using MAPI and CDO 1.21 in managed code…

...

Okay, I've heard that before so why exactly is using MAPI or CDO 1.21 not supported in managed code?

MAPI has its own memory management model that conflicts with and is incompatible with the .NET runtime. This the primary reason that MAPI and CDO 1.21 are not supported running in a .NET process. The common symptoms you will see are seemingly random Access Violations and very often memory leaks (especially with CDO 1.21). There is no methodology for avoiding or managing these symptoms by using interop libraries or managing references in a particular fashion in your .NET code – it just won't work.

The trap is that CDO 1.21 and .NET can "appear" to work and you can get pretty far in your dev cycle before you run into problems. Many times we see this come up in soon after a solution is released to production, in late cycle performance testing, or in a pilot program. ...

...

Fine, I won't use .NET and MAPI or CDO 1.21 in the same process but I still need to write this application – now what?

The simple answer is you either need to not use .NET or not use MAPI or CDO 1.21. So how do you make that decision?

...

...If you really feel that CDO 1.21 or MAPI is your best option based on the business requirements of what your application must do then by all means use CDO 1.21 – just plan to use it *out of process* from your .NET code."

So in short create an out of proc ActiveX EXE in VB6 (or C++, etc) to contain your MAPI/CDO code and access it via interop...

Wednesday, August 01, 2007

Standalone Downloads for Collaboration Data Objects (CDO) 1.2.1 and MAPI Client Libraries

Microsoft DownloadsCollaboration Data Objects, version 1.2.1

"Beginning in Exchange 2007 Beta 2 and Outlook 2007 Beta 2, CDO 1.2.1 will no longer be provided as a part of the install of the product. As a result, there is functionality missing that many applications depend upon. CDO 1.2.1 is a package providing access to Outlook-compatible objects through a COM-based API.

..."

Microsoft DownloadsMicrosoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1

"Starting with Exchange 2007, neither the Messaging API (MAPI) client libraries nor CDO 1.2.1 are provided as a part of the base product installation. As a result, there is functionality missing that many applications depend on. Microsoft Exchange MAPI and CDO 1.2.1 provide access to these APIs, which, in turn, provide access to the contents of MAPI stores

...

The Messaging API is a COM-like API that provides access to the contents of messaging stores. CDO 1.2.1 (Collaboration Data Objects, version 1.2.1) is a package providing access to Outlook-compatible objects through a COM-based API. Using either CDO or MAPI, a program can connect to a MAPI store, and then perform operations against that store. Starting with Exchange 2007, Microsoft will distribute the MAPI client libraries and CDO 1.2.1 as a Web download

..."

I know I'm going to need these downloads one day in the not too distant future...

Wednesday, June 07, 2006

Security Prompt Gone from Outlook 2007 Object Model (Almost)

What's New for Developers in Microsoft Office Outlook 2007 (Part 1 of 2)

"...
Security
Outlook 2007 introduces an important change in the way that the Outlook object model guard operates. While the behavior of the object model guard has not changed significantly for Outlook add-ins, Outlook 2007 allows external applications to run without object model guard prompts-provided that the computer on which your code is running has functional antivirus software installed and that all antivirus definitions are current.

This change represents a major departure from the way the object model guard worked in previous versions for external out-of-process COM callers. Before Outlook 2007, external COM callers were always untrusted from the perspective of the object model guard. This means that external applications had to resort to extended MAPI or third-party libraries in order to prevent the display of Outlook 2007 object model guard warnings, such as the one shown in Figure 3.


Outlook Address Book warning

Figure 3. Outlook Address Book warning

The object model guard was originally introduced for Microsoft Outlook 98 and Microsoft Outlook 2000. Since the introduction of the object model guard, the frequency of the Address Book warning often frustrated developers for legitimate external COM applications and their users. Also, if you needed to use CDO for MAPI property access or improved performance, you faced a different security model that did not integrate with the Outlook add-in trust model. For most applications, Outlook 2007 has removed the need for CDO. Outlook 2007 offers improved security that aims at removing development road blocks for all legitimate Outlook developers. The following sections describe the operation of the Outlook object model guard in Outlook 2007.

....


Out-of-Process Callers and the Outlook Object Model Guard
For out-of-process callers, the behavior has changed significantly from Outlook 2003. If antivirus software has been installed and is up-to-date on the client computer, Outlook will not display object model guard warning dialogs when you call protected members such as MailItem.Send or MailItem.Recipients.

All out-of-process COM callers and add-ins will run without security prompts under the following conditions:

  • The client computer is running Microsoft Windows XP SP2 or Microsoft Windows Vista and the Windows Security Center indicates that the antivirus software is in a "Good" health status. If the computer is joined to a domain, this health status indicator may not be visible, but will still be maintained.
  • The installed antivirus software is designed for Windows XP SP2 or Windows Vista.
  • Outlook is configured in one of the following ways:

    • Uses the default security settings
    • Uses group policy-defined security settings that are set to warn when no antivirus software is detected
    • Uses group policy-defined security settings that do not have programmatic access policy applied
Additionally, Outlook will suppress the prompts when it has been configured to Never warn me about suspicious activity (not recommended) through the Trust Center dialog box ..."

This is huge! (For me and other out of process Outlook developers at least).

Working around Outlook security eats up way too much development time... This feature alone will drive me to push for Outlook 2007.

Tuesday, November 01, 2005

Outlook Redemption 4 Released

“Redemption 4.0.0.452
Version 4.0 of Redemption includes a completely new library: RDO (Redemption Data Objects) that can function as a complete replacement of the CDO 1.21 library.

While Safe*Item Redemption objects are designed to be used with either Outlook Object Model or CDO 1.21 objects to work around the security prompts with minimum modifications to the existing code, RDO is designed to provide a complete functionality replacement for CDO 1.21, which besides being blocked by the security patch, also hasn't been updated (functionality-wise) for almost 10 years.

RDO blends the low level access of CDO 1.21 with the functionality of the Outlook Object Model. It can be used from any code: COM add-ins, EXEs, scripts, Windows Services, etc. It can be used in any language that supports IDispatch-friendly objects (VB, VB Script, Java, .Net languages, C/C++, Delphi, etc).
 
For the complete documentation, see http://www.dimastr.com/redemption/rdo/

If you are doing ANY Outlook/MAPI/CDO development, then you owe it to yourself to check out Outlook Redemption. This is a must have tool…

Today I heard the 4.0 has been released and that there’s now a new very cool library called Redemption Data Objects (RDO – Which reminds me of old RDO – Remote Data Objects, but that’s just cause I’ve been VB Man since V1…)

I could have really used this about 6 months ago when I migrated an Outlook 2000 (pre-Security SP) to Outlook 2003. Talk about painful…

Anyway, this sounds VERY cool and I’m glad to see Redemption continue to improve with age.

For more information about Outlook Redemption, see http://www.dimastr.com/redemption

Friday, September 09, 2005

VB.NET DLL Wrapper For C MAPIEx Extended MAPI

The Code Project - VB.NET wrapper for DLL of C MAPIEx Extended MAPI - VB.NET

"Since first encountering the 'Outlook Security Update', which has mangled many an important production VB program, I've wished for a better way to work around it in VB.

Sadly, there is still not a functional, direct VB way around that travesty. But programs can be brought back online in an 'Updated' Outlook environment with P/Invoke wrapping a DLL written in C++ to access the Extended MAPI calls.

The attached source is a wrapper to call the MAPIEx.dll library written by Noel Dillabough (as per the 08/25/2005 update to Noel's CMAPIEx article...which was posted but pending update as of this writing). The DLL must either be registered or in the working directory for this VB program to work."


One of these days I'll be needing Extended MAPI interface, preferable via VB.Net... While I really like Outlook Redemption, I'd rather not have to play in the COM world when I move to/rewrite in .Net.

Extended MAPI is much harder to use than OOM, CDO or Outlook Redemption, but you get so much closer to the raw data... In the last few years, as my EDD apps have matured, I've been moving closer and closer to ExMAPI. Now I get by with a mix of CDO, OOM, Redemption and ExMAPI, which just makes me crazy. I think it might be worth the effort to dive all the wave into the ExMAPI pool.

We'll see...

Thursday, April 28, 2005

Outlook 2003: Integration API Reference

Download details: Outlook 2003: Integration API Reference

"The Microsoft Office Outlook 2003 Integration API Reference contains comprehensive documentation for different sets of APIs that allow third-party developers to extend and integrate with Microsoft Office Outlook 2003 Service Pack 1. This documentation contains reference materials for the Outlook 2003 Integration APIs, including the Account Management API, the Data Degradation Layer API, the Free/Busy API, the MAPI-MIME Conversion API, the Offline State API, the Replication API, and the Store API."

From the document:
The Outlook 2003 Integration API Reference contains comprehensive documentation for five sets of APIs that allow third-party developers to extend and integrate with Microsoft Office Outlook 2003 Service Pack 1:

The Account Management API provides access to user account information and notifications of account changes.

The Connection State API supports Outlook callbacks, notifying clients of changes in a user's connection state in Outlook—for example, from being offline to being online in Outlook.

The Free/Busy API provides free/busy status information about specific user accounts within a specific time range.

The MAPI-MIME Conversion API supports conversion between MIME objects and MAPI messages.

The Store API provides miscellaneous store functionality

... "


Packaged as a CHM, this provides overview and detailed information (with C++ code snips) on the above API's.

If you need this (and you'll probably know it if you do), this is good poop. If not, then it's not very useful...


Wednesday, October 13, 2004

Saturday, May 29, 2004

MAPIViewer v2.0 - daveswebsite.com

MAPIViewer v2.0 - daveswebsite.com

"MAPIViewer is a simple Windows NT/2000/XP utility that provides an Explorer-like interface for browsing MAPI stores. If you are working with the MAPI api's, then this is a MUST HAVE utility for viewing MAPI stores, folders, and message item properties, and hierarchy.

MAPIViewer allows for the viewing and modification of a MAPI database accessible via the win32 MAPI API's. This latest release displays message attachments and recipients, profiles, and status tables."

Saturday, May 01, 2004

NetXP 3.0

Home

From FTP, to UI (Task/Action Panes), FTP, MAPI, WNet to WinAPI...

Free for personal use or use in freeware applications, $120 to purchase.

(via The Daily Grind