Blocking Security pop ups

[Guest]

Managers in my company are going to be using a macro to delegate a large
number of tasks to a large number of employees. Each employee could get 10-30
tasks every day, at the onset, and about 5-10 after some "cleaning up." The
only thing I want them to have to click is accept for each of these tasks.
How do I block the following security pop up:

"A program is trying to access e-mail addresses you have stored in Outlook.
Do you want to allow this? If this is unexpected, it may be a virus and you
should choose No. "

Any ideas?

 

[Rob Nicholson]

How do I block the following security pop up:

"A program is trying to access e-mail addresses you have stored in
Outlook.
Do you want to allow this? If this is unexpected, it may be a virus and
you
should choose No. "

This is part of the Outlook security mechanism. If you're using Exchange as
your backend server, then the following will help:

http://office.microsoft.com/en-us/assistance/CH011480701033.aspx

Other alternatives are things like Redemption:

http://office.microsoft.com/en-us/assistance/CH011480701033.aspx

Or other 3rd party utilities which effectively press OK for you (not that
nice).

Cheers, Rob.

 

[Ken Slovak - [MVP - Outlook]]

The correct URL for Redemption is www.dimastr.com/redemption. There is also
comprehensive information about the security model and how to avoid it at
http://www.outlookcode.com/d/sec.htm.

 

[Guest]

http://www.outlookcode.com/d/sec.htm.
-- This was the exact answer I was looking for. Thank you very much. I
haven't tested it yet, because I'm too busy with other things today, but from
what I can see, I'm sure it will work perfect. I did use the redemption code
and it compiled just fine, so hopefully we are good. Thank you again. I've
been working on this particular hang up for a good week now.

 

[Rob Nicholson]

http://www.outlookcode.com/d/sec.htm.

Useful link - thanks. We're having a devil of a time getting Outlook
security template working at a client (seems to ignore CheckAdminSettings or
the public folder) and I suspect they are not using Outlook 2003 SP1 as
mentioned in this article.

Cheers, Rob/