Platform SDK: Exchange 2000 Server

Using Default Configuration Settings

[This is preliminary documentation and subject to change.]

When a Configuration object is created, default values are loaded. The following sections discuss these default configuration values.

Local SMTP/NNTP Service

If the Microsoft SMTP and/or NNTP Service is installed on the local computer, CDO sets the SMTP pickup directory to the directory defined in the service properties, and sets the delivery method to use the pickup directory.

Outlook Express

If Microsoft® Outlook® Express is installed on the local computer, CDO gets default configuration settings from the Outlook Express properties defined for the default identity of the default account.

Because CDO automatically collects configuration information from the computer, you may not need to set these values manually. For example, if either the SMTP service or Outlook Express is installed, your application can send messages without having to explicitly configure the Message object. To change these settings, you can start with the default values and modify the fields you desire. Use the IConfiguration.Load method to load particular default settings on demand.

Note   For performance reasons, it is recommended that you manually set up a single Configuration object and associate it with all messages rather than relying on defaults. Loading defaults for each message is an expensive operation and if you let CDO load defaults for each sent message, performance can be adversely affected. For example, if using CDO in an ASP application, you can store the Configuration class instance in the Session object, and then reuse it for each message sent during that session. If you use global settings, you could also place the object in the Application object.