Managing the MTA transaction log files

When the  channel option is enabled,  all MTA message  transaction log entries are made to the file    in the MTA log directory, of MS 7.0.5 DATAROOT ; (prior to MS 7.0, the MTA message transaction log file was located via the   MTA Tailor option). If connection logging is enabled via the    MTA option, connection  transaction log entries are also by default written to the    file, but if the MTA option    has been set, then the connection transaction log entries will instead  be written to the   file.

The message , which the  Scheduler is typically configured to run  every night shortly after midnight,  appends any existing    to the cumulative log file,   , renames the current    file to  ,  and then begins a new   file. It also performs the analogous operations for any    files. (In older versions of the MTA, the names and location of these log files were controlled by the,  , and     MTA Tailor options; as of MS 7.0.5, these names are not configurable and the location is derived from the   value.)  (Note that the    MTA option can modify the frequency of such transaction log file "roll over".)

Note that the MTA itself by default never does anything to the cumulative   file; it is up to each site to manage  that log file however they choose, whether by periodically saving it to  backup, deleting it, truncating it, or the like.

When considering how to manage the log files, note that the MTA periodic    will execute a site-supplied  DATAROOT  shell script, if  one exists. Thus some sites may choose to supply their own   that, for instance, renames the old    file once a week (or once a month), etc. (Note that the  MTA option can modify the frequency at which such "cleanup" is performed.)

See also:
 * log_connection MTA Option
 * separate_connection_log MTA Option
 * Scheduler task options
 * Scheduler options
 * Special symbolic names
 * return_split_period MTA Option
 * return_cleanup_period MTA Option
 * MTA transaction logging