Logging

Logged data can be output to the file or to the syslog system service. Output destination is defined in the configuration file of Dr.Web MailD, in the [Logging] section.

When syslog is used, every string looks as follows:

'['tid']' name[.sub] level [sid(/mta-id)] text

where:

•tid - identifier of the thread which is responsible for string output;

•name - name of the component which performs an output (for example, plug-in or module name);

•sub - name of the component service to perform output.

The most important services are:

oipc - interprocess communication service;

othrN - support service of the thread pool with the N number;

oreport - report support service;

oldap, odbc, oracle, sqlite, mysql, postgres, cdb, berkeley, firebird - support service of the corresponding Lookups;

ocontrol - interactive management service;

oparser - notification templates parser service;

oMRS - service of receiving messages via SMTP/LMTP;

osmtp - service of sending messages via SMTP;

olmtp - service of sending messages via LMTP;

opipe - service of sending messages through the pipe;

oqueue - service of processing internal queue.

•level - log verbosity level. The following values are available: FATAL, ERROR, WARN, INFO, DEBUG.

•sid - session identifier of a message to which that log line is related. The number must be specified in hexadecimal notation;

•mta-id - identifier of a message inside MTA, from which this message is received. It is output only if Dr.Web MailD is not operating in SMTP/LMTP proxy mode and the identifier was received from MTA;

•text - text of a log message.