25.3.2 Enabling MTA Logging

To gather statistics for just a few particular MTA channels, enable the logging channel keyword on just those MTA channels of interest. Many sites prefer to enable logging on all MTA channels. In particular, if you are trying to track down problems, the first step in diagnosing some problems is to notice that messages are not going to the channel you expected or intended, and having logging enabled for all channels can help you investigate such problems.

To Enable MTA Logging on a Specific Channel

1. Edit the imta.cnf file.

   The file is located in the /opt/SUNWmsgsr/config directory.

2. To enable logging for a particular channel, add the logging keyword to the channel definition. For example:

   channel-name keyword1 keyword2 logging

   In addition, you can also set a number of configuration parameters such as directory path for log files, log levels, an so on. See 25.4 Managing Message Store, Admin, and Default Service Logs

   ---

   Note –

   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. It also performs the analogous operations for any connection.log* files. It is possible that mail.log_yesterday contains time stamps which have already passed over rotation time.

   ---

To Enable MTA Logging on All Channels

1. Edit the imta.cnf file.

   The file is located in the /opt/SUNWmsgsr/config directory.

2. Add the logging keyword to your defaults channel configuration file (see 12.1 Configuring Channel Defaults). For example:

   defaults logging notices 1 2 4 7 copywarnpost copysendpost postheadonly noswitchchannel immnonurgent maxjobs 7 defaulthost siroe.com siroe.com ! ! delivery channel to local /var/mail store l subdirs 20 viaaliasrequired maxjobs 7 pool LOCAL_POOL mailhost.siroe.com