-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> [EMAIL PROTECTED] wrote:
>>
>> I haven't looked into the SapiMapi subproject too much, but it looks
>> like
>> it is basically intended for similar purposes.
>
> SapiMapi is a testing utility put together to analyse
> Mapi objects and properties in m
[EMAIL PROTECTED] wrote:
I haven't looked into the SapiMapi subproject too much, but it looks like
it is basically intended for similar purposes.
SapiMapi is a testing utility put together to analyse
Mapi objects and properties in memory. I couldn't use
OutSpy because it relied on Outlook properl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I don't think this actually went to the list. Sorry if it did and this
results in a duplicate response.
Regards,
Jason Nocks
- Original Message
Subject: Re: [otlkcon-devel] undocumented
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> [EMAIL PROTECTED] wrote:
>> A simple example is MAPI named properties. Technically, named properties
>> are *optional*. A MAPI message store doesn't need to support named
>> properties according to the MAPI documentation. But, if you want to work
>>
[EMAIL PROTECTED] wrote:
there's all of the undocumented MAPI properties that Outlook
*requires*, plus the "optional" MAPI stuff that Outlook *requires*, etc.
can you please make me some example?
I would like to see which kind of Outlook features aren't available if
you code a standard MAPI-compli
