Read Email Addresses Without Warning

  • Thread starter Thread starter Fred Block
  • Start date Start date
F

Fred Block

Hi All,

I'm writing an application that creates an Outlook email (via a VB6
application). My code is listing the Distribution Lists names it finds in a
ListBox so the user can select one. I noticed that if I attempt to get the
email addresses (using "AddressEntries") a warning pops up. I was hoping to
get around this if the user wants the list of email addresses displayed so
they know they've selected the correct list.

Also - is it correct to simply pass the Distribution list name to the "To"
property of the MailItem to get the email sent to all members in that list?

Thanks in advance for your help!

- Fred
 
Hi,

Regarding the passage of items to the To: field, check
your lisbox properties, and remember that if you have it
set to accept multiple selections, you could end up with
users producing email with cumbersome To: lines (unless
only the name of the Dist. list appears in the actual
message - and your 'review' feature is in the form of a
msgbox, balloon, or something similar).

Also, are you reading from a .pab or .wab, or some other
address source?

What is the warning?

The Distribution list name appears to Outlook as a person
with a lot of addresses (as I understand and experience
it), so as long as it passes Outlook's authentication (it
IS a valid populated list), it should go through as
though you had entered Joe Schmoe's name in the To:
field. Outlook will check the name (person or Dist.
list), and supply the message header with the
corresponding address entry (or entries, in the case of a
list).

Disclaimer: Though I have substancial MSO and VB
experience, I am NOT a pro with Outlook, so wait a bit
for more advice please.

Sincerely,

Matthew

=}
 
Yes, your usage of the DL name is correct.

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