Although most message services will provide entry point functions and MAPI strongly recommends that they do, these functions are not strictly required. Message services can provide access to configuration data in other ways. However, using an entry point function standardizes and simplifies the process of configuration.
MAPI expects all message service entry point functions to be able to store and retrieve properties from the profile sections that are associated with their message service. You can support this functionality interactively, programmatically, or both interactively and programmatically.
To support interactive configuration, provide a property sheet that displays the properties involved in configuring your message service. As an option, you can also supply property sheets for each configurable provider. Some message services restrict users to a read-only view of configuration properties; other message services allow them to make changes.
To support programmatic configuration, your message service entry point function must be able to work without user intervention. If your message service can be called by the Profile Wizard, you must support programmatic configuration. If your message service does not allow itself to be configured with the Profile Wizard, you can choose whether or not to support programmatic configuration.
For more information about how to support configuration in a message service entry point function, see MSGSERVICEENTRY.
PR_SERVICE_ENTRY_NAME=<name of message service>