Access messages in Outlook WARNING

  • Thread starter Thread starter Keith Davis
  • Start date Start date
K

Keith Davis

I just installed the update from Microsoft described as
Office XP Service Pack 3 (SP3). Since I did that,
everytime I open Microsoft Outlook 2002 I receive a
warning message that "A program is trying to access
addresses you have stored in Outlook." Then I have to
indicate whether YES or NO I want to allow the access.
Since I have a firewall and NAV that is updated daily, I
highly suspect the problem is Outlook finding itself
trying to access Contacts or some other internal issue.
Anybody seen a fix for this?

Thanks, Keith
 
The security dialogs that pop up when an application tries to access certain
Outlook properties and methods are designed to inhibit the spread of viruses
via Outlook; see http://www.slipstick.com/outlook/esecup.htm#autosec. They
cannot be simply turned on or off with a user option or registry setting.

However, Outlook 2003 does not show security prompts on three specific types
of applications:

-- VBScript code in published, non-oneoff Outlook forms

-- Outlook VBA code that uses the intrinsic Application object

-- Outlook COM add-ins properly constructed to derive all objects from
the Application object passed by the OnConnection event

In earlier versions of Outlook, standalone users can use a free tool called
Express ClickYes (http://www.express-soft.com/mailmate/clickyes.html) to
click the security dialog buttons automatically. Beware that this means if a
virus tries to send mail using Outlook or gain access to your address book,
it will succeed.

If you're the administrator in an Exchange Server environment, you can
reduce the impact of the security prompts with administrative tools. See
http://www.slipstick.com/outlook/esecup/admin.htm

If it's an application you wrote yourself and either your application needs
to support versions besides Outlook 2003 or your application runs extenal to
Outlook, you have these options for modifying your program to avoid the
security prompts (roughly in order of preference):

-- Use Extended MAPI (see http://www.slipstick.com/dev/mapi.htm) and C++
or Delphi; this is the most secure method and the only one that Microsoft
recommends. However, it applies only to COM add-ins and external programs;
you cannot use Extended MAPI in Outlook forms or VBA.

-- Use Redemption (http://www.dimastr.com/redemption/), a third-party
COM library that wraps around Extended MAPI but parallels the Outlook Object
Model, providing many methods that the Outlook model does not support

-- Use SendKeys to "click" the buttons on the security dialogs that your
application may trigger. See
http://www.slipstick.com/outlook/esecup.htm#autosec for a link to sample
code.

-- Program the free Express ClickYes
(http://www.express-soft.com/mailmate/clickyes.html) tool to start suspended
and turn it on only when your program needs to have the buttons clicked
automatically.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
 
i have the same problem--of course it's understanable that you can't
simply Turn Off Security in Outlook. however, Outlook's implementation
is so bad that it borders on useless. "A PROGRAM is trying to
access..."?? could it be more vague?

and the options: Yes (allow for up to, gasp, 10 whole minutes??) or
No. brilliant. anyone at Microsoft even consider that some programs
should ALWAYS have the right? and i'm not installing a bunch of other
garbage on my machine to click buttons on stupid and--so far--entirely
inappropriate dialog boxes. (and, as you mentioned Sue, this is
effectively turning OFF the security for when you might actually need
it.)


wondering, Keith, if you have Cloudmark's SpamNet installed? i do, and
am wondering if Outlook is confusing it with something unwanted?

i also have NAV, so that's a possibility as well. also ZoneAlarm, in
addition to the firewall built into my router.

do we have any of these others in common?

thanks!
 
Actually the problem started happening to us also on all our Office
2003 and Office XP with SP3 machines. The only way we have found to
bypass this problem is to go to Tools/Options/Mail Format and check
the "Use Microsoft Office Word to edit e-mail address". We were
getting the warning messages everytime we wrote an e-mail or sometimes
on certain replies also. If anyone knows why this happens and how to
correct it, e-mail me at (e-mail address removed). In the meantime
hope this solves your problem.


remazerov said:
I agree with the other complainers. This is an absolutely AWFUL situation. THIS MUST BE CHANGED IMMEDIATELY or it will render Outlook useless as an email editor. There was another suggestion that we disable Word as the email editor. How ludicrous!

Everybody makes mistakes. THIS change in Outlook is a mistake. Please correct your mistake. We'll be willing to live with security issues through NAV and other anti-virus programs and anti-spam programs. What you've done is make a good program unusable. Please fix it or you're going to get zillions of complaints from disgruntled users.




----- Sue Mosher [MVP-Outlook] wrote: -----

The security dialogs that pop up when an application tries to access certain
Outlook properties and methods are designed to inhibit the spread of viruses
via Outlook; see http://www.slipstick.com/outlook/esecup.htm#autosec. They
cannot be simply turned on or off with a user option or registry setting.

However, Outlook 2003 does not show security prompts on three specific types
of applications:

-- VBScript code in published, non-oneoff Outlook forms

-- Outlook VBA code that uses the intrinsic Application object

-- Outlook COM add-ins properly constructed to derive all objects from
the Application object passed by the OnConnection event

In earlier versions of Outlook, standalone users can use a free tool called
Express ClickYes (http://www.express-soft.com/mailmate/clickyes.html) to
click the security dialog buttons automatically. Beware that this means if a
virus tries to send mail using Outlook or gain access to your address book,
it will succeed.

If you're the administrator in an Exchange Server environment, you can
reduce the impact of the security prompts with administrative tools. See
http://www.slipstick.com/outlook/esecup/admin.htm

If it's an application you wrote yourself and either your application needs
to support versions besides Outlook 2003 or your application runs extenal to
Outlook, you have these options for modifying your program to avoid the
security prompts (roughly in order of preference):

-- Use Extended MAPI (see http://www.slipstick.com/dev/mapi.htm) and C++
or Delphi; this is the most secure method and the only one that Microsoft
recommends. However, it applies only to COM add-ins and external programs;
you cannot use Extended MAPI in Outlook forms or VBA.

-- Use Redemption (http://www.dimastr.com/redemption/), a third-party
COM library that wraps around Extended MAPI but parallels the Outlook Object
Model, providing many methods that the Outlook model does not support

-- Use SendKeys to "click" the buttons on the security dialogs that your
application may trigger. See
http://www.slipstick.com/outlook/esecup.htm#autosec for a link to sample
code.

-- Program the free Express ClickYes
(http://www.express-soft.com/mailmate/clickyes.html) tool to start suspended
and turn it on only when your program needs to have the buttons clicked
automatically.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers



Keith Davis said:
I just installed the update from Microsoft described as
Office XP Service Pack 3 (SP3). Since I did that,
everytime I open Microsoft Outlook 2002 I receive a
warning message that "A program is trying to access
addresses you have stored in Outlook." Then I have to
indicate whether YES or NO I want to allow the access.
Since I have a firewall and NAV that is updated daily, I
highly suspect the problem is Outlook finding itself
trying to access Contacts or some other internal issue.
Anybody seen a fix for this?
Click to expand...
Click to expand...
 
It could be the Adobe PDF Maker add-in. See
http://www.slipstick.com/outlook/ol2002sp3.htm#problems

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers



Gus Rendon said:
Actually the problem started happening to us also on all our Office
2003 and Office XP with SP3 machines. The only way we have found to
bypass this problem is to go to Tools/Options/Mail Format and check
the "Use Microsoft Office Word to edit e-mail address". We were
getting the warning messages everytime we wrote an e-mail or sometimes
on certain replies also. If anyone knows why this happens and how to
correct it, e-mail me at (e-mail address removed). In the meantime
hope this solves your problem.


remazerov <[email protected]> wrote in message
Click to expand...
situation. THIS MUST BE CHANGED IMMEDIATELY or it will render Outlook
useless as an email editor. There was another suggestion that we disable
Word as the email editor. How ludicrous!correct your mistake. We'll be willing to live with security issues through
NAV and other anti-virus programs and anti-spam programs. What you've done
is make a good program unusable. Please fix it or you're going to get
zillions of complaints from disgruntled users.
----- Sue Mosher [MVP-Outlook] wrote: -----

The security dialogs that pop up when an application tries to access certain
Outlook properties and methods are designed to inhibit the spread of viruses
via Outlook; see http://www.slipstick.com/outlook/esecup.htm#autosec. They
cannot be simply turned on or off with a user option or registry setting.

However, Outlook 2003 does not show security prompts on three specific types
of applications:

-- VBScript code in published, non-oneoff Outlook forms

-- Outlook VBA code that uses the intrinsic Application object

-- Outlook COM add-ins properly constructed to derive all objects from
the Application object passed by the OnConnection event

In earlier versions of Outlook, standalone users can use a free tool called
Express ClickYes (http://www.express-soft.com/mailmate/clickyes.html) to
click the security dialog buttons automatically. Beware that this means if a
virus tries to send mail using Outlook or gain access to your address book,
it will succeed.

If you're the administrator in an Exchange Server environment, you can
reduce the impact of the security prompts with administrative tools. See
http://www.slipstick.com/outlook/esecup/admin.htm

If it's an application you wrote yourself and either your application needs
to support versions besides Outlook 2003 or your application runs extenal to
Outlook, you have these options for modifying your program to avoid the
security prompts (roughly in order of preference):

-- Use Extended MAPI (see http://www.slipstick.com/dev/mapi.htm) and C++
or Delphi; this is the most secure method and the only one that Microsoft
recommends. However, it applies only to COM add-ins and external programs;
you cannot use Extended MAPI in Outlook forms or VBA.

-- Use Redemption (http://www.dimastr.com/redemption/), a third-party
COM library that wraps around Extended MAPI but parallels the Outlook Object
Model, providing many methods that the Outlook model does not support

-- Use SendKeys to "click" the buttons on the security dialogs that your
application may trigger. See
http://www.slipstick.com/outlook/esecup.htm#autosec for a link to sample
code.

-- Program the free Express ClickYes
(http://www.express-soft.com/mailmate/clickyes.html) tool to start suspended
and turn it on only when your program needs to have the buttons clicked
automatically.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers



I just installed the update from Microsoft described as
Office XP Service Pack 3 (SP3). Since I did that,
everytime I open Microsoft Outlook 2002 I receive a
warning message that "A program is trying to access
addresses you have stored in Outlook." Then I have to
indicate whether YES or NO I want to allow the access.
Since I have a firewall and NAV that is updated daily, I
highly suspect the problem is Outlook finding itself
trying to access Contacts or some other internal issue.
Anybody seen a fix for this?
Thanks, Keith
Click to expand...
Click to expand...
Click to expand...
 
Back
Top