PMDF System Manager's Guide

The format of the log file is subject to change. Currently, by default, each log file entry contains eight or nine fields,¹ e.g.,

19-Jan-2012 19:16:57.64 l tcp_local E 1 adam@acme.com rfc822;marlowe@examplex.com marlowe@examplex.com 1 2 3 4 5 6 7 8 9

These fields are:

1. The date and time when the entry was made, written in standard OpenVMS date and time format.
2. The channel name for the source channel. (For the Printer channel, the first 32 characters of the print queue name are logged.)
3. The channel name for the destination channel. (For SMTP channels when LOG_CONNECTION is enabled, a plus, +, indicates inbound to the SMTP server; a minus, -, indicates outbound via the SMTP client.)
4. The type of entry; see Table 31-1.
5. The size of the message. This is expressed in kilobytes by default, although this default can be changed by using the BLOCK_SIZE keyword in the PMDF option file. (For the Printer channel, the size field displays the job entry number on OpenVMS, and is always 0 on UNIX. For the MAILSERV channel, the size field is always 0. For the Pager channel, the size field is the number of pages sent.)
6. The envelope From: address. Note that for messages with an empty envelope From: address, such as notification messages, this field will be blank.
7. The original form of the envelope To: address.
8. The active (current) form of the envelope To: address.
9. The delivery status (SMTP channels only).

Table 31-1 Logging Entry Codes

Entry	Description
General
D	Successful dequeue
DA	Successful dequeue with SASL (authentication)
DS	Successful dequeue with TLS (security)
DSA	Successful dequeue with TLS and SASL (security and authentication)
E	Enqueue
EA	Successful enqueue with SASL (authentication)
ES	Successful enqueue with TLS (security)
ESA	Successful enqueue with TLS and SASL (security and authentication)
J	Rejection of attempted enqueue (rejection by slave channel program)
K	Used instead of R or W when a warning, failure, or bounce message should be generated, but the sender asked not to be notified of such events.
Q	Temporary failure to dequeue
R	Recipient address rejected on attempted dequeue (rejection by master channel program), or generation of a failure/bounce message
W	Warning message generated regarding a not-yet-delivered message
Z	Some successful recipients, but this recipient was temporarily unsuccessful; the original message file of all recipients was dequeued, and in its place a new message file for this and other unsuccessful recipients will be immediately reenqueued
SMTP channels' LOG_CONNECTION + or - entries
C	Connection closed
O	Connection opened
X	Connection rejected
Y	Connection try failed before being established
I	ETRN command received
IMAP, POP, and POPPASSD server connection entries
A	Authentication attempt failed
O	Login phase completed (either successful login or aborted connection)
C	Connection closed cleanly
X	Connection aborted (by either end)+
MAILSERV channel
F	Error processing command; command not executed
S	Command successfully executed
Printer channel
A	Print request failed
S	Print request succeeded
Pager channel
A	Aborted (permanent error)
F	Temporary failure
R	Page rejected (permanent error)
S	Success
PMDF-FAX G3_TO_FAX and FAX_TO_DATA channels
A	Delivery attempt aborted, message requeued (temporary error)
F	Delivery failed (permanent error)
M	Maximum number of delivery attempts exceeded, message not requeued (permanent error)
S	Success

PMDF may optionally be configured to log additional information to the log file; see the LOG_* PMDF options described in Section 7.2. With LOG_CONNECTION, LOG_FILENAME, LOG_MESSAGE_ID, LOG_NODE, LOG_NOTARY, LOG_PROCESS, and LOG_USERNAME all enabled, the format becomes as follows. (Note that the sample log entry line has been wrapped for typographic reasons; the actual log entry would appear on one physical line.)

19-Jan-2012 13:13:27.10 NODEA 2e2d.1 tcp_local l E 1 service@examplex.com rfc822;adam@acme.com 1 10 11 2 3 4 5 6 7 adam 276 PMDF_QUEUE:[l]ZZ01IWFY9ELGWM00094D.00;1 <01IWFVYLGTS499EC9Y@examplex.com> SYSTEM 8 12 13 14 15 examplex.com (examplex.com [192.168.253.66]) 16 9

Where the additional fields, beyond those already discussed above, are:

10. The name of the node on which the channel process is running.
11. The process id (expressed in hexadecimal), followed by a period (dot) character and a count. If this had been a multithreaded channel entry (e.g., a tcp_* channel entry), there would also be a thread id present between the process id and the count.
12. The NOTARY (delivery receipt request) flags for the message, expressed as an integer.
13. The file name in the PMDF queue area.
14. The message id.
15. The username of the executing process. Note that in the case of Dispatcher services such as the SMTP server, this will be the username of the last person to startup the Dispatcher.
16. This connection information consists of the sending system or channel name, such as the name presented by the sending system on the HELO/EHLO line (for incoming SMTP messages), or the enqueuing channel's official host name (for other sorts of channels). In the case of TCP/IP channels, the sending system's "real" name, that is, the symbolic name as reported by a DNS reverse lookup and/or the IP address, can also be reported within parentheses as controlled by the ident* channel keywords; see Section 2.3.4.40. This sample assumes use of one of these keywords, for instance us of the default identnone keyword, that selects display of both the name found from the DNS and IP address.