Re: Spamnet add-in to Outlook

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Sue Mosher [MVP-Outlook] (suemvp_at_outlookcode.com)
Date: 10/28/04 

Date: Thu, 28 Oct 2004 17:31:05 -0400

Anything is possible, but given that SpamNet works fine without prompts
under the default trust mechanism built into Outlook 2003, their code
doesn't seem to be the problem.

Are you sure you trusted the correct .dll? If I were you, I'd be discussing
this issue with CloudMark.

My guess about PDFMOutlook.dll is that it is not properly constructed to
take advantage of the trust mechanism. 

-- 
Sue Mosher, Outlook MVP
Author of
     Microsoft Outlook Programming - Jumpstart for
     Administrators, Power Users, and Developers
     http://www.outlookcode.com/jumpstart.aspx
"tdog" <tdog@discussions.microsoft.com> wrote in message 
news:B143F1E1-BA65-4ABD-B794-62DF2DE8EF98@microsoft.com...
> Sue,
> Thanks for the response. The Outlook Security Settings folder is in the
> Public folder structure in Exchange, the affected clients have the proper
> CheckAdminSettings value in the Registry (it was also set up to address 
> the
> PDFMOutlook.dll issue which produces similar pop-ups, and it does fix that
> issue if you have certain Programmatic Settings approved - trusting the 
> DLL
> in Trusted Code does nothing), yet we still have many users getting the
> security model pop-ups in OL2003 when SpamNet 3.0 is installed.
>
> I have read in several places that OL2003 allegedly trusts COM add-ins;
> however, we are not the only users experiencing the problem (and we don't
> have ActiveSync installed, which according to Cloudmark can cause the 
> SpamNet
> add-in to trigger the pop-ups).
>
> Could there be an issue with the SpamNet DLL coding such that Outlook does
> not recognize it (and thus not trust it) correctly?
>
> Thanks.
>
> "Sue Mosher [MVP-Outlook]" wrote:
>
>> Sounds like the trust mechanism isn't working, either because the folder 
>> is
>> in the wrong place, the required client registry entry isn't set, etc. In
>> any case, Outlook 2003 trusts COM add-ins by default. In other words, if
>> SpamNet is the only reason you fired up that folder, you don't need it.
>>
>> "tdog" <tdog@discussions.microsoft.com> wrote in message
>> news:545F4D6C-1D5C-4252-AF42-A5BFBB04EFD1@microsoft.com...
>> > Hello,
>> >
>> > I and other enterprise users are running Outlook 2003 with SpamNet 3.0 
>> > and
>> > we get the "A program is trying to access e-mail addresses..." pop-up.
>> > This
>> > occurs even though we have trusted spamnet.dll in our Outlook Security
>> > Template per the reference in the Cloudmark Knowledge Base which points 
>> > to
>> > the Microsoft ORK article. ActiveSync is not installed on my system and
>> > never
>> > has been (brand-new system).
>> >
>> > Has anyone else had any luck getting the trust to work for the SpamNet
>> > plug-in? Thanks!
>> >
>> > cheers /td
>>
>>
>>

Relevant Pages

  • Re: Spamnet add-in to Outlook
    ... Sounds like the trust mechanism isn't working, ... SpamNet is the only reason you fired up that folder, ... Sue Mosher, Outlook MVP ...
    (microsoft.public.outlook.program_addins)
  • Re: Spamnet add-in to Outlook
    ... I agree that setting up the Outlook Security Template and not ... utilizing the default security may cause SpamNet to trigger the pop-ups. ... The best scenario, then, is probably to use NO Security Template but allow ... > under the default trust mechanism built into Outlook 2003, ...
    (microsoft.public.outlook.program_addins)
  • Re: word could not create the work file. check temp environment va
    ... Also Outlook 2003. ... click Word Options and in the Trust Center ... settings, click the Trust Center Settings button ... In the Macro Settings, select "Disable all macros with notification" ...
    (microsoft.public.word.application.errors)
  • Re: AFDS, Domain trust or other?
    ... ADFS won't help with Outlook here, ... understanding that this is just for web applications in its current state. ... intrusive than doing the trust). ... I've an exchange systems in my domain. ...
    (microsoft.public.windows.server.active_directory)
  • Re: The day of reckoning is almost upon me.....
    ... >> Sure, trust the MS firewall, for as long as it takes to get Zone Alarm ... A good firewall should give you the option to stop everything connecting to the ... If the curt and continual advice of your peers ain't enough to ... circumcise you from Outlook Egregious you're blind to the bat signal. ...
    (uk.sport.football)