outlook 2003 ?

  • Thread starter Thread starter Josh
  • Start date Start date
J

Josh

I am running active directory replication monitor from the support tools on
a work station. I configured it to send me emails when there is a problem.
TO do so I had to install outlook 2003 and Collaborative data objects. It
works good other than when it wants to send a mail it prompts me. The idea
with this work station is that it is automated. How can I work around this
feature inside outlook to allow this computer to send mail when there is a
problem?
 
Don't use the object models in Outlook 2003, Collaboration Data Objects
1.21(s), or Simple MAPI to send the message. There are security measures
that prohibit the collection of email address and the sending of mail w/out
the user acknowledging the send.

Couple of thoughts at this point...

* If you have an Exchange 2000/2003 server on hand, take the CDO.DLL file
from the server and place it on the client. (you need to unregister the
existing CDO.DLL on the client and then register the one you grabbed from
the Exchange server). Any patches you apply to Outlook will require you to
perform the same steps.

* Uninstall Office/Outlook 2003 and install Office/Outlook 2000 and don't go
past SR1. Patches/Updates after this point will include the enhanced
security features.

* Contact the vendor of the monitor and ask if it will support sending
messages via CDO for Windows 2000. (This does not require you to install
the SMTP service that is part of IIS.)
 
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
 
Back
Top