D
David Clark
Outlook 2003 has severely restricted the object model for S/MIME encrypted
messages, signed messages with S/MIME receipt requests, and S/MIME receipts.
In particular, attempting to do an Item.Display (or Reply or Forward) will
result in error 0x80040F04, 0x80040F01 and 0x80040F02 respectively for each
of these message types. These errors occur even for trusted COM add-ins.
I can understand the object model guarding the contents of an encrypted
message, but don't understand the security risk related to displaying an
encrypted message to the user, especially for a trusted COM add-in. IMO this
seriously cripples the usefulness of Outlook automation.
Any additional information regarding this change in Outlook 2003 behavior
and/or possible workarounds would be greatly appreciated.
BTW, this behavior exists in both Outlook 2003 RTM and SP1.
Thanks,
David
messages, signed messages with S/MIME receipt requests, and S/MIME receipts.
In particular, attempting to do an Item.Display (or Reply or Forward) will
result in error 0x80040F04, 0x80040F01 and 0x80040F02 respectively for each
of these message types. These errors occur even for trusted COM add-ins.
I can understand the object model guarding the contents of an encrypted
message, but don't understand the security risk related to displaying an
encrypted message to the user, especially for a trusted COM add-in. IMO this
seriously cripples the usefulness of Outlook automation.
Any additional information regarding this change in Outlook 2003 behavior
and/or possible workarounds would be greatly appreciated.
BTW, this behavior exists in both Outlook 2003 RTM and SP1.
Thanks,
David