Logging, nologging, logheader Channel Options

From MsgServerDocWiki

Message transaction logging (logging, nologging, logheader)

The MTA provides facilities for logging each message as it is enqueued and dequeued. All log entries are made to the file mail.log_current in the MTA log directory, (i.e., msg-install-path/data/log/mail.log_current). Logging is controlled on a per-channel basis. The logging channel option activates logging for a particular channel while the nologging channel option disables it. Logging is disabled on all channels by default although most default configurations enable logging on all channels.

The message return job, which runs every night around midnight, appends any existing mail.log_yesterday to the cumulative log file, mail.log, renames the current mail.log_current file to mail.log_yesterday, and then begins a new mail.log_current file. Note that the MTA itself never does anything to the cumulative mail.log file and it is up to each site to manage (e.g., delete, truncate, backup, etc.) that log file however they choose.

If you wish to have all of your channels log message activity to the logging file, then simply add the logging channel option to a defaults channel.

When logging is enabled, the (new in JES MS 6.0) logheader option may be used on source channels to additionally enable logging of message headers. It takes an encoded integer argument, where bit 0 (value 1) causes logging during dequeue operations, and setting both bits 0 and 1 (value 3) causes logging during enqueue operations. The specific header lines to be logged are controlled by the log_headers.opt file.

Use with msadmin

Enable HTTP transaction logging for the msadmind server.

The default value in this context is: 0

Use with channel