File Structure

 Top  Previous  Next

The configuration file has the following structure:

•File content is divided into named sections. Possible names of these sections are strictly predefined and cannot be changed. The section name is specified in square brackets and is similar to the component name Dr.Web for UNIX Mail Servers, which uses the section parameters (except for [Root] section , which stores all parameters of the configuration daemon Dr.Web ConfigD).

•The ';' or '#' characters in the configuration file indicate the beginning of a comment—all text following the characters is skipped by components Dr.Web for UNIX Mail Servers while reading configuration parameters.

•One line of the file can contain only one parameter value. The general format of specifying the value is as follows (white spaces before and after the character '=' are ignored):

<Parameter name> = <Value>

•All parameter names are strictly predefined and cannot be changed.

•All section and parameter names are case-insensitive. Parameter values, except for names of directories and files in paths (for UNIX-like OS) are also case-insensitive.

•Order in which sections are specified in the file and order in which parameters are specified in the section are of no importance.

•Parameter values in the configuration file can be enclosed in quotation marks, and must be enclosed in quotation marks if they have white spaces

•Some parameters can have a list of values. If so, the values are either separated with commas or specified several times in different lines of the configuration file. In the former case, white spaces around a comma are ignored. If a white space character is a part of a parameter value, the character must be enclosed in quotation marks.

Example of how to specify several values for one parameter:

1)As a comma-separated list:

Parameter = Value1, Value2,"Value 3"

2)In different lines of the configuration file:

Parameter = Value2
Parameter = Value1
Parameter = "Value 3"

Note that the order in which parameter values are specified is of no importance.

If parameter values are paths, then each listed parameter value must be put between quotation marks if the listing of components via commas is used. For example, if the parameter ExcludedPaths requires two paths /etc/file1 and /etc/file2, then this parameter must be written into a configuration file either as a string

ExcludedPaths = "/etc/file1", "/etc/file2"

or as two strings

ExcludedPaths = /etc/file1
ExcludedPaths = /etc/file2

Otherwise, the component that uses this parameter can interpret the string '/etc/file1, /etc/file2‘ as one path.

•If a parameter can have more than one values, it is designated explicitly. So, if this is not explicitly designated in the current manual or within the comments in the configuration file, the parameter can have only one value.

For description of the configuration file sections, see description of Dr.Web for UNIX Mail Servers components.