In addition to the basic information always provided when logging is enabled, you can specify that additional, optional information fields be included by setting various LOG_* MTA options in the MTA Option file. The file specified with the IMTA_OPTION_FILE option in the IMTA tailor file (msg_svr_base/config/imta_tailor) specifies the MTA Option file. By default, this is the msg_svr_base/config/option.dat file.
For complete details about the MTA Option file, see the Option File in Sun Java System Messaging Server 6 2005Q4 Administration Reference.
Edit the MTA Option file.
Set the LOG_MESSAGES_SYSLOG option to 1.
A value of 0 is the default and indicates that syslog (event log) logging is not performed.
Edit the MTA Option file.
Set the LOG_MESSAGE_ID option to 1.
A value of 0 is the default and indicates that message IDs are not saved in the mail.log file.
Edit the MTA Option file.
Set the LOG_FILENAME option to 1.
This option makes it easier to immediately spot how many times the delivery of a particular message file has been retried. This option can also be useful in understanding when the MTA does or does not split a message to multiple recipients into separate message file copies on disk.
Edit the MTA Option file.
Set the LOG_CONNECTION option.
This option causes the MTA to log TCP/IP connections, as well as message traffic. The connection log entries are written to the mail.log* files by default. Optionally, the connection log entries can be written to connection.log* files. See the SEPARATE_CONNECTION_LOG option for more information.
Edit the MTA Option file.
Set the SEPARATE_CONNECTION_LOG option to 1.
Use this option to specify that connection log entries instead be written to connection.log files. The default value of 0 causes the connection logging to be stored in the MTA log files.
Edit the MTA Option file.
When used in conjunction with LOG_CONNECTION, this option enables correlation by process ID of which connection entries correspond to which message entries.