The options listed in this section affect PMDF logging, monitoring, and counters. The CIRCUITCHECK_COMPLETED_BINS option relates to PMDF circuit check counter binning. The LOG_DELAY_BINS and LOG_SIZE_BINS options relate to PMDF counters binning. The LOG_SNDOPR option can be set by sites that want to have OPCOM messages (OpenVMS) or syslog messages (UNIX) or event log entries (NT) in cases of logging or counters updating problems. OpenVMS sites that have heavy message traffic logged to the PMDF log file can find it useful to adjust the LOG_ALQ and LOG_DEQ option so that the underlying file allocation uses larger extents. The rest of these logging options affect the formatting of the PMDF log file and logging of optional additional information.
CIRCUITCHECK_COMPLETED_BINS (comma-separated list of up to eight integers)This option specifies the bin divisions, in seconds, for the PMDF circuit check counters. The default values are 120, 300, 900, 1800, 3600, 7200, 14400, and 28800; i.e., two minutes, five minutes, fifteen minutes, thirty minutes, one hour, two hours, four hours, and eight hours, respectively.
LOG_ALQ (integer; OpenVMS only)The LOG_ALQ option specifies the default allocation quantity (in OpenVMS blocks) for the PMDF log file,
mail.log_current. The default value is 2000, or twice the LOG_DEQ value if LOG_DEQ has been explicitly set. On a busy system that is updating that log file frequently, increasing this value can provide increased efficiency.
LOG_CONNECTION (integer)The LOG_CONNECTION option controls whether or not connection information, e.g., the domain name of the SMTP client sending the message, is saved in the
mail.logfile. This value is a decimal integer representing a bit-encoded integer, the interpretation of which is given in the table below.
Bit Value Usage 0 1 When set, connection information is included in E, D and R log records. 1 2 When set, connection open/close/fail records are logged by message enqueue and dequeue agents such as the SMTP and X.400 clients and servers. This bit also enables use of the $T flag (for causing logging) in PORT_ACCESS rejection entries. 2 4 When set,
Irecords are logged recording ETRN events.
4 16 When set, C entries can include site-supplied text from a PORT_ACCESS mapping table entry.
mail.log_current. The default value is 1000. On a busy system that is updating that log file frequently, increasing this value can provide increased efficiency.
mail.logfile. A value of 1 enables file name logging. When file name logging is enabled, the file name will appear as the first field after the final form envelope To: address. A value of 0 (the default) disables file name logging.
mail.logfile. A value of 1 (the default) is the standard format. A value of 2 requests non-null formatting: empty address fields are converted to the string "<>". A value of 3 requests counted formatting: all variable length fields are preceded by "N:", where "N" is a count of the number of characters in the field.
mail.logfile. A value of 1 enables message header logging. The specific headers written to the log file are controlled by a site-supplied
log_header.optfile. The format of this file is that of other PMDF header option files; see Section 2.3.7. For instance, a
To: MAXIMUM=1 From: MAXIMUM=1 Defaults: MAXIMUM=-1
mail.logfile. A value of 1 enables message ID logging. When message ID logging is enabled, the message ID will be logged after the final form envelope To: address entry---and after the message file name, if LOG_FILENAME=1 is also enabled. A value of 0 (the default) disables message ID logging.
mail.logfile. This can be useful information when PMDF is running in a multi-node cluster. A value of 1 enables node name logging. When the node name is logged, it will appear as the first field following the date and time stamps in log entries. A value of 0 (the default) disables node name logging.
mail.logfile entries. A value of 1 enables NOTARY flag logging. A value of 0 (the default) disables it. The NOTARY flags will be logged as a bit encoded integer after the current form of the envelope To: address.
mail.logfile. A value of 1 enables process id logging. A value of 0 (the default) disables it. The process id will be logged after the date and time stamps in log entries---and after the node name, if LOG_NODE=1 is also enabled. The process id field itself will consist of the process id in a hexadecimal representation followed by a period, next in the case of a multithreaded channel the thread id followed by a period, followed by a counter. That is, in the case of a single threaded channel
mail.logfile. Note that messages submitted via SMTP with authentication (SMTP AUTH) will be considered to be owned by the username that authenticated, prefixed with the asterisk,
*, character. A value of 1 enables username logging. When username logging is enabled, the username will be logged after the final form envelope To: address field in log entries---and after the message ID, if LOG_MESSAGE_ID=1 is also enabled. A value of 0 (the default) disables username logging.
mail.log*, or stored separately in
connection.log*files. SEPARATE_CONNECTION_LOG=0, the default, causes connection logging to be stored in the regular message log files; a value of 1 causes the connection logging to be stored separately.