there's a detailed description on msdn that's been out there since 2000 when
the outlook security patch was released. it describes the problem and
resolution. essencially, you need to digitally sign your assembly and update
you security settings to allow your signatured app full reign for your
"zone".
i've never been a fan of using outlook to send email programmaticall y, so of
course i have to recommend simply opening port 25 and send your email via
standard email rfc commands.
cuts a lot of crap out of the picture.
hth,
steve
"Christian Hamel" <ch************ @NOSPAMvideotro n.ca> wrote in message
news:ec******** ******@TK2MSFTN GP12.phx.gbl...
As said in the topic?
I understand that this security has been added following many viruses out
there but we have an automated system that we need to put in place that
send emails.
Any idea?
Thanks