The configuration file has the following structure.
•The 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 the Dr.Web for UNIX Mail Servers component name, 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 the Dr.Web for UNIX Mail Servers components while reading configuration parameters.
•Each of the lines in the file can contain only one parameter value:
<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.
•The order of sections in the file as well as the order of parameters inside the sections 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 take multiple 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.
You can specify multiple values as:
1)а comma-separated list:
Parameter = Value1, Value2,"Value 3" |
2)а sequence of lines in the configuration file:
Parameter = Value2 |
The order of values is arbitrary.
|
Path to files and directories are always enclosed into quotation marks when separated by commas, e.g:
If you represent as a set of path as a sequence of lines, quotation marks are not necessary:
|
•If a parameter can take multiple values, it is indicated in the comments in the configuration file or in the text of the current manual.
For description of the configuration file sections, see description of the Dr.Web for UNIX Mail Servers components.