in reply to MS Outlook Win32::OLE Security Problem After Office SP3

Microsoft completely bulldozed the MAPI interface some couple of years ago now (been a while since you added any service packs ;-). This was their (ill thought out) response to all the email worms that were/still are causing havoc. It caused every untrusted (ie non M$) app that used MAPI to explode and no fix was available at the time.

If you are accessing Exchange mailboxes then there is a security (un)patch that undoes this prompting by allowing you to make your script TRUSTED CODE. If you are accessing PSTs I don't think there is any fix (I could not find one ~8 months ago) but that may have changed.

Have a look at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnout2k2/html/odc_olsecurityovw.asp and do a search for 'MAPI outlook trusted code' or similar on google.

cheers

tachyon

  • Comment on Re: MS Outlook Win32::OLE Security Problem After Office SP3

Replies are listed 'Best First'.
Re: MS Outlook Win32::OLE Security Problem After Office SP3
by jonadab (Parson) on Feb 03, 2004 at 06:02 UTC
    Microsoft completely bulldozed the MAPI interface some couple of years ago now

    Of course, it would be too much trouble to just do what every other mailreader in the universe does and just display the message (rather than attempt to execute it). No, that would be too obvious and straightforward.


    $;=sub{$/};@;=map{my($a,$b)=($_,$;);$;=sub{$a.$b->()}} split//,".rekcah lreP rehtona tsuJ";$\=$ ;->();print$/