S
Shivprasad Kotagal
Hi Outlook Developers & Gurus,
I need some help with a Outlook VBA COM Add-In. Outlook 2002 gave me two
kind of warnings whenever the COM Add-in kicked in and executed.
1. A program is trying to automatically send e-mail on your behalf....
2. A program is trying to access e-mail addresses you have stored....
I tried the Microsoft Recommended method to get rid of the warnings,
referring to the articles Microsoft Knowledge Base Article - 290498, 290499
.. I installed the Outlook Security Administrator Package, declared the COM
Addin as a 'trusted code' in the default security settings form published in
a public folder 'Oulook Security Settings'. Now, the warning no.1 dosent
appear, but warning no. 2 still does. I dont understand what is going
wrong. I checked that the 'Application' object being used through out the
COM Addin is the same. The warning comes up when the code tries to get the
'current user'. The COM Add-in does not use CDO methods anywhere. The
CheckAdminSettings registry key is also installed fine on the client
computers. I can use Redemption and modify the code, but why is not the
Microsoft recommended Method of declaring the COM Add-In as a trusted code
working to eliminate all the security pop-ups. Any suggestions please
...................
Best regards,
Shivprasad Kotagal
I need some help with a Outlook VBA COM Add-In. Outlook 2002 gave me two
kind of warnings whenever the COM Add-in kicked in and executed.
1. A program is trying to automatically send e-mail on your behalf....
2. A program is trying to access e-mail addresses you have stored....
I tried the Microsoft Recommended method to get rid of the warnings,
referring to the articles Microsoft Knowledge Base Article - 290498, 290499
.. I installed the Outlook Security Administrator Package, declared the COM
Addin as a 'trusted code' in the default security settings form published in
a public folder 'Oulook Security Settings'. Now, the warning no.1 dosent
appear, but warning no. 2 still does. I dont understand what is going
wrong. I checked that the 'Application' object being used through out the
COM Addin is the same. The warning comes up when the code tries to get the
'current user'. The COM Add-in does not use CDO methods anywhere. The
CheckAdminSettings registry key is also installed fine on the client
computers. I can use Redemption and modify the code, but why is not the
Microsoft recommended Method of declaring the COM Add-In as a trusted code
working to eliminate all the security pop-ups. Any suggestions please
...................
Best regards,
Shivprasad Kotagal