Loglevel Option

From Messaging Server Technical Reference Wiki
Jump to: navigation, search


Updated in release: 7 Update 1


The loglevel option can be: nolog, emergency, alert, critical, error, warning, notice, information, or debug. This is ignored by the Dispatcher and Job Controller unless the use_nslog option is set for them, and ignored by the MMP if use_nslog is set to 0.


The default value is: notice

Use with logfile

The loglevel  logfile option specifies the logging level for the whatever component's logfile it is set under. E.g., imap.logfile.loglevel specifies the logging level for the IMAP server's log file.

Valid values for the loglevel option are: nolog, emergency, alert, critical, error, warning, notice, information, or debug. The default is notice.

The loglevel logfile option for the MTA specifies an MTA log level used for the imta log file (primarily used by ims_master and the LMTP server).


The default value in this context is: notice


See also:

Use with ens

The loglevel ENS option specifies the level of ENS client library logging to the process nslog file. Messages are also filtered per the loglevel of the process. Allowed values are as in the Unified Configuration logfile.loglevel option (logfile.*.loglevel in legacy configuration). But note that the value "debug" generates lots of data and is not recommended.


The default value in this context is: information


See also:

Use with messagetrace

Legacy Message Trace data is inherently information level. So setting the messagetrace.loglevel option to a higher value than information will suppress the recording of Message Trace data. Data in the transactlog is inherently critical level.


See also:

Use with mta

The mta.logfile.loglevel option is ignored by the Dispatcher and Job Controller unless the dispatcher.use_nslog and job_controller.use_nslog options are set for them, respectively.

Note that this MTA-wide setting of mta.logfile.loglevel (by default affecting both ims-ms channels and the LMTP server) can be overridden for the LMTP server via a tcp_lmtp_server.loglevel setting.

Also note that the mta.loglevel option is defined and can be set to the same set of values, but as of MS 8.0.1.2 it is a no-op. It's behavior in previous version is erratic - in some cases it works and mta.logfile.loglevel does not, in other cases the value is ignored.


The default value in this context is: notice


See also:

Use with the MMP

The MMP's loglevel option can be: nolog, emergency, alert, critical, error, warning, notice, information or debug. Note that loglevel will be ignored by the MMP if use_nslog is set to 0.

The MMP will not generate messages with priority higher than 'error'. For backwards compatibility, MMP configuration files may use integer settings from 3 to 7 for 'error' to 'debug' respectively, or 0 for 'nolog'.


The default value in this context is: notice


See also:

Use with the IMAP proxy

The IMAP Proxy loglevel option can be: nolog, emergency, alert, crticial, error, warning, notice, information or debug. The MMP will not generate messages with priority higher than 'error'.


The default value in this context is: notice


See also:

Use with the POP proxy

The POP Proxy loglevel option can be: nolog, emergency, alert, crticial, error, warning, notice, information or debug. The MMP will not generate messages with priority higher than 'error'.


The default value in this context is: notice


See also:


See also: