Actually, neither CDO 1.21 nor Simple MAPI is suitable for unattended operation involving sending messages through Outlook, because when run on a machine that has Outlook installed, they'll trigger security prompts. Your description confirms what I said earlier, that for your scenario, CDO for Windows (CDOSYS) would be the right API to use. Ask your vendor if that's an option.

If not, then you might need to remove Outlook and install some other mail program that can be accessed with Simple MAPI but doesn't have Outlook's security against malicious mailers. If you're working in an Exchange environment, installing Exchange System Manager should give you a version of CDO 1.21 that won't trigger prompts; see http://support.microsoft.com/kb/171440/.

As for logging on, CDO 1.21 can use dynamic profile information; see http://support.microsoft.com/kb/195662/en-us. Another article, http://support.microsoft.com/kb/306962/, provides a way to create a named, stored profile without installing Outlook.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx


wrote in message .. .
On Tue, 7 Feb 2006 14:38:29 -0500, Sue Mosher [MVP-Outlook] wrote:

Depends on what you mean by "logged onto server"? What kind of server? If all you want to do is send messages, Extended MAPI and CDO 1.21 are not the best choices for API. CDO for Windows would be better.

I have app that runs as a service. Nobody need to bee loged onto server.
This app has ability to generate mail using simple MAPI or CDO by
connecting to Outlook profile. App vendor say that if I want to use sending
mail by simple MAPI or CDO, that there must be user looged on server,
otherwise it would not work.