PMDF System Manager's Guide

This section lists options relating to OpenVMS user agents such as VMS MAIL, PMDF MAIL, and DECwindows MAIL.

DELIVERY_RECEIPT_OFF (string; OpenVMS only)

This option is used to specify a special RFC 822 comment string used in IN% addresses in VMS MAIL to disable any requests for a delivery receipt. The default if this option is not specified is:

(NO-DELIVERY-RECEIPT)

The enclosing parentheses are required and must be specified in the option value.

DELIVERY_RECEIPT_ON (string; OpenVMS only)

This option is used to specify a special RFC 822 comment string used in IN% addresses in VMS MAIL to request a delivery receipt. The default if this option is not specified is:

(DELIVERY-RECEIPT)

The enclosing parentheses are required and must be specified in the option value.

DIS_NESTING (non-negative integer; OpenVMS only)

The DIS_NESTING option controls how many nesting levels PMDF allows in the expansion of VMS MAIL distribution lists. A value of 0 disables the ability to use VMS MAIL distribution lists. Currently this option only affects the PMDF MAIL utility. The default value for this option is 20.

FORM_NAMES (list of comma separated strings; OpenVMS only)

Multiple values should be separated with commas but not with spaces. The default is "FAX-FORM,PH-FORM,X500-FORM".

MAIL_DELIVERY_FILENAME (string)

The MAIL_DELIVERY_FILENAME option sets the actual filename used by users to store message delivery option information. The default name is mail.delivery if this option is not used to change the name. No device or directory can be specified here; these files are always located in users' home directories.

MISSING_ADDRESS (string)

This option can be used to specify the address to insert in the VMS MAIL From: header if no From: address was originally present; the default is missing-address@no.where.

MP_SIGNED_MODE (0 or 1)

The MP_SIGNED_MODE option controls whether or not PMDF interprets (parses) messages of type multipart/signed. The default is 0, which means PMDF treats the message as opaque. The risk in parsing multipart/signed messages is that the exact content would most likely change when PMDF re-assembles the message, thus invalidating the signature.

MULTINET_MM_EXCLUSIVE (-3 to 3; OpenVMS only)

This option is documented for historical reasons only; delivery to MultiNet MM is no longer supported. (Prior to PMDF V5.2, the local channel supported delivery to MultiNet MM as an alternative to delivery to VMS MAIL.) The MULTINET_MM_EXCLUSIVE option controls whether or not PMDF's local channel delivers exclusively to MultiNet MM or not. Possible values are:

Value	Usage
-3	Never deliver mail to MultiNet MM mailboxes.
-2	Not used at present; do not specify.
-1	Deliver mail to MultiNet MM mailboxes only if MultiNet MM is specified as part of the user's profile information.
0	Deliver mail to MultiNet MM mailboxes if the user has the appropriate MultiNet MM mailbox files in his or her home directory.
+1	Deliver mail to the user's Multinet MM mailbox by default unless the user's profile information specifies some other type of delivery.
+2	Not used at present; do not specify.
+3	Deliver mail to the user's Multinet MM mailbox unconditionally.

The default is -1, which means that MultiNet MM delivery will be used only when the user has profiled MultiNet MM as his or her preferred mailbox format.

READ_RECEIPT_OFF (string; OpenVMS only)

This option is used to specify a special RFC 822 comment string used in IN% addresses in VMS MAIL to disable any requests for a read receipt. The default if this option is not specified is:

(NO-READ-RECEIPT)

The enclosing parentheses are required and must be specified in the option value.

READ_RECEIPT_ON (string; OpenVMS only)

This option is used to specify a special RFC 822 comment string used in IN% addresses in VMS MAIL to request a read receipt. The default if this option is not specified is:

(READ-RECEIPT)

The enclosing parentheses are required and must be specified in the option value.

SAFE_TCL_MODE (0--3)

This option is a bit encoded integer. The lowest bit, when set, allows components of PMDF to interpret message parts of type application/safe-tcl upon user confirmation. (At present, PMDF MAIL is the only component of PMDF which supports Safe-Tcl.) The second lowest bit, when set, puts PMDF's Safe-Tcl interpreter into a very paranoid mode in which it will not allow information from sensitive message header lines to be disclosed to Safe-Tcl scripts. The default value for this option is 3 which allows Safe-Tcl scripts to be executed upon user confirmation, but does so in paranoid mode.

USE_MAIL_DELIVERY (0 or 1)

The USE_MAIL_DELIVERY option controls whether or not PMDF checks to see if a given user has a mail.delivery file in their home directory and, if the file exists, uses it to direct message delivery operations on the local channel for the user. The default is 1, which means that PMDF will check for these files. A value of 0 will disable consultation of mail.delivery files.

VMS_MAIL_EXCLUSIVE (-3 to 3; OpenVMS only)

This option is documented for historical reasons only; delivery to MultiNet MM is no longer supported. (Prior to PMDF V5.2, the local channel supported delivery to MultiNet MM as an alternative to delivery to VMS MAIL.) The VMS_MAIL_EXCLUSIVE option controls whether or not PMDF's local channel delivers exclusively to VMS MAIL or not. Possible values are:

Value	Usage
-3	Never deliver mail to VMS MAIL mailboxes.
-2	Not used at present; do not specify.
-1	Deliver mail to VMS MAIL mailboxes only if VMS MAIL is specified as part of the user's profile information.
0	Deliver mail to VMS MAIL mailboxes unless the user has some other sort of mailbox in his or her home directory or has specified some other kind of delivery as part of his or her profile information.
+1	Deliver mail to the user's VMS MAIL mailbox by default unless the user's profile information specifies some other type of delivery.
+2	Not used at present; do not specify.
+3	Deliver mail to the user's VMS MAIL mailbox unconditionally.

The default is 0, which means that either VMS MAIL is used unless a given user has the necessary MultiNet MM files in his or her home directory or has profiled the use of MultiNet MM.