let me further explain the situation, we have our software which can batch import. that is installed on the workstation, currently when they do that security warning continously pops up. i thought i saw somewhere that you could allow certain applications to access outlook and send mail through them. we are running outlook 2003 with server 2003.
> On the server side, you wouldn't send through Outlook at all. You can use
> CDO for Windows to accomplish this, sending directly through an SMTP server.
[quoted text clipped - 9 lines]
> >
> > thomas
In Outlook 2003, properly constructed COM add-ins do not trigger security
prompts at all unless the network administrator has implemented the Exchange
security settings folder as a tool for managing Outlook security. If they're
going that route, then they can designate individual COM add-ins as
"trusted."
No other programs other than properly constructed Outlook COM add-ins can be
trusted. Is your application a COM add-in and do all its Outlook objects
derive from the Application object passed in the OnConnection event?
Repeating: You do not need Outlook if your primary is to send mail.

Signature
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx
> let me further explain the situation, we have our software which can batch import. that is installed on the workstation, currently when they do that
security warning continously pops up. i thought i saw somewhere that you
could allow certain applications to access outlook and send mail through
them. we are running outlook 2003 with server 2003.
> > On the server side, you wouldn't send through Outlook at all. You can use
> > CDO for Windows to accomplish this, sending directly through an SMTP server.
[quoted text clipped - 5 lines]
> > side but i would like to do this from server side, b/c the client side
> > programs just sends the email and doesnt care what program is sending it.