Outlook COM Addin and MAPI Provider
 

Hi

I have a MAPI message store which works perfectly with Outlook 2007 but not
with 2003. The problem I'm having with it is that HTML messages don't render
in OL2003. I can't find any properties which could lead to this and I have
tried a lot of properties.

The MAPI provider has a helper COM add in written in C++. I've managed to
get it working by making the COM plugin read the MAPI property PR_HTML and
setting it as the HTML body via the OOM.

This works. But as far as I can see all it does it add two MAPI properties
OutlookVersion and another OutlookVersion property (InternalOutlookVersion)
with a string property. Setting these properties manually has no effect (
with the correct GUID for MAPI named properties ).

The only other thing I can think of is that the HTML editor property in the
OOM gets set when the COM plugin sets the body via the OOM. This is NULL
otherwise ( even in OL2007 though it works in OL2007 without it ).

Also the EntryID in MAPI ( PR_ENTRYID ) is clearly visible for my messages
but in the OOM the entry ID is shown as blank. I can't imagine what would
cause this.

Could anyone shed any light on these problems?

Cheers
Win

Outlook COM Addin and MAPI Provider
 

I can't tell you what the problem is in your code
but you can try to find out it using my utility MAPISpy www.mapispy.com
..
Compare logs from your provider and logs from PST provider.

Regrads
Henry

Windoze:
Hi

I have a MAPI message store which works perfectly with Outlook 2007 but not
with 2003. The problem I'm having with it is that HTML messages don't render
in OL2003. I can't find any properties which could lead to this and I have
tried a lot of properties.

The MAPI provider has a helper COM add in written in C++. I've managed to
get it working by making the COM plugin read the MAPI property PR_HTML and
setting it as the HTML body via the OOM.

This works. But as far as I can see all it does it add two MAPI properties
OutlookVersion and another OutlookVersion property (InternalOutlookVersion)
with a string property. Setting these properties manually has no effect (
with the correct GUID for MAPI named properties ).

The only other thing I can think of is that the HTML editor property in the
OOM gets set when the COM plugin sets the body via the OOM. This is NULL
otherwise ( even in OL2007 though it works in OL2007 without it ).

Also the EntryID in MAPI ( PR_ENTRYID ) is clearly visible for my messages
but in the OOM the entry ID is shown as blank. I can't imagine what would
cause this.

Could anyone shed any light on these problems?

Cheers
Win