Ha! He is anti Microsoft everything and his biggest basis for this is
"Windows has too many security issues." Outlook, included, in his book.
So, theoretically, if I am using some non-secure way to access Outlook
features then it would be no problem for some adware, virus, or
unscrupulous internet predator to see that going on and tap into my
computer to start sending spam or flooding us with pop-ups.

That's what HE says. I really don't see how, but he's the boss. Anyway,
we agreed for me to use it for a few days and see if anything "pops up!"

Dmitry Streblechenko wrote:
I don't think I understand your IT guy: how exactly would it be a security
risk if your custom script uses CDO which is already installed and you are
not installing any additional software?
I have a pretty wild imagination, but I just can't come up with a scenatio
that can even remotely be considered a security risk.

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"Davideo" wrote in message
...
Thanks! I am just automating an Excel ss so that when something is
received or ready to ship, it sends out a quick message alerting the
appropriate people. Seems to be working so far, but our IT guy
(anti-Windows everything) is leery about security.

Michael Bauer [MVP - Outlook] wrote:
Seems that I didn't understand your question the first time. If you're
talking about CDO 1.21 then it doesn't matter whether you're automating
Outlook directly or via CDO. And if Outlook is installed and configured
then
I can't imagine that it should be more unsecure to use it.

What I was talking about is the security feature that applies to both:
When
you try to send an e-mail or access one of the blocked properties (like
e-mail addresses) from a outside of Outlook then a message box pops up.
To
avoid that I recommended the Redemption.