Configuration syntax

In Unified Configuration, nearly all configuration options are stored in the  Message Server unified configuration file,  as XML elements; a few, security-related, options (e.g., unix user ids) are stored instead in the    file. However, under normal circumstances, the Messaging Server unified configuration file    is not---indeed should not be--- inspected or  editted manually by the Messaging Server administrator. Instead, normally Messaging Server&#x27;s   utility is used to examine the configuration  and make configuration changes.

Options in the unified configuration file  generally are typed XML elements. The  utility performs type checking on configuration settings it makes. See Option value syntax for further details.

The  and   options discussed in Options for migrating to Unified Configuration set the context for option values.

Sets of commands for  may be scripted using the Recipe language.

A few special symbolic names may be used in option values, or in the Recipe langauge.

Another language used by multiple components of Messaging Server, including the MTA and the Message Store (for purge operations), as well as by external components such as some email user agents, is the Sieve language.

Several components of Messaging Server make use of the TCP wrapper concept, for access controls.

See also:
 * msconfig utility
 * Option value syntax
 * Options for migrating to Unified Configuration
 * Special symbolic names
 * Recipe language
 * Sieve filters
 * TCP wrappers
 * restricted.cnf file