PMDF System Manager's Guide
Previous Contents Index

7.3.1 Addresses, Aliases, Headers, and Rewriting Options

The options described in this section affect and modify various aspects of PMDF address, alias, and rewriting handling, and the information placed in certain sorts of headers.

ALIAS_DOMAINS (integer)

This option takes a bit encoded integer argument controlling the format of alias file and alias database lookups. The default value is 1, meaning that alias file and alias database lookups probe with only the local part (mailbox portion) of the address. Note that for addresses matching the local channel, such a probe is made even if bit 0 (value 1) is not set. Setting bit 1 (value 2) causes a probe to be made using the entire address (including the domain name). Setting bit 2 (value 4) causes a wildcard * probe to be made, (akin to the sort of wildcard * probe made when doing a directory channel crdb lookup). If all bits are set, i.e., ALIAS_DOMAINS=7, then the order of the probes is to first probe with the entire address (the most specific check), next probe with a wildcard * local part plus the domain name, and finally probe with just the local part.
Bit Value Usage
0 1 Look up localpart. Clearing this bit disables the lookup of local parts only for channels other than the local channel; for the local channel, local parts are always looked up.
1 2 Look up localpart@ domainname.
2 4 Try an * lookup if no exact match is found.
Bit 0 is the least significant bit.
Note that by default only addresses rewritten to the local channel are checked against the alias file and alias database. However, via use of the aliaslocal channel keyword it is possible to cause addresses matching other channels to be checked against the alias file and alias database.

EXPROUTE_FORWARD (integer 0 or 1)

This option controls the application of the exproute channel keyword to forward-pointing (To:, Cc:, and Bcc: lines) addresses in the message header. A value of 1 is the default and specifies that exproute should affect forward-pointing header addresses. A value of 0 disables the action of the exproute keyword on forward-pointing addresses.

ID_DOMAIN (string)

The ID_DOMAIN specifies the domain name to use when constructing message IDs. By default, the official host name of the local channel is used.

IMPROUTE_FORWARD (integer 0 or 1)

This option controls the application of the improute channel keyword to forward-pointing (To:, Cc:, and Bcc: lines) addresses in the message header. A value of 1 is the default and specifies that improute should affect forward-pointing header addresses. A value of 0 disables the action of the improute keyword on forward-pointing addresses.

MAIL_OFF (string)

Specify the comment string that disables mail delivery for list addresses. The default is NOMAIL .

MAX_ALIAS_LEVELS (integer)

The MAX_ALIAS_LEVELS option controls the degree of indirection allowed in aliases, that is, how deeply aliases can be nested, with one alias referring to another alias, etc. The default value is 10.

MAX_INLINE_DIR_LEVELS (integer)

The MAX_INLINE_DIR_LEVELS option controls the degree of indirection allowed in directory channel inline lookups, that is, how deeply directory channel aliases can be nested, with one directory channel entry referring to another directory channel entry, etc. The default value is 10. Note that this option only applies when the inline channel keyword is used on the directory channel.

MISSING_RECIPIENT_POLICY (integer)

According to RFC 822, messages are required to contain at least one recipient header: a To: , Cc: , or Bcc: header. This RFC states that a message without any such headers is illegal. This requirement has been relaxed in the updated RFC 2822 standard: such messages are no longer illegal. However, some remote systems that conform to RFC 822 will not accept these messages. In many cases, it can be useful to have PMDF modify the message to include at least one recipient header. The MISSING_RECIPIENT_POLICY option takes an integer value specifying what approach to use for such messages; the default value, if the option is not explicitly present, is 1, meaning that no action is taken.
Value Action
1 Pass the message through unchanged
2 Place envelope To: recipients in a To: header
3 Place all envelope To: recipients in a single Bcc: header
4 Generate an empty group construct To: header (i.e. "To: Recipients not specified: ;")
5 Generate a blank Bcc: header
6 Reject the message
Note that the The missingrecipientpolicy channel keyword, discussed in Section 2.3.4.48, can be used to set per-channel controls for this sort of behavior.

NAME_TABLE_NAME (string; OpenVMS only)

The NAME_TABLE_NAME option specifies the name of a logical name table to be searched for address aliases by PMDF. This table name can itself be a logical name (in the process or system directory) which specifies one or more tables to search. This option has no default; if it is not specified logical name tables are not searched for aliases.

RECEIVED_DOMAIN (string)

The RECEIVED_DOMAIN option sets the domain name to use when constructing Received: headers. By default, the offical host name of the local channel is used.

REVERSE_ENVELOPE (0 or 1)

The REVERSE_ENVELOPE option controls whether or not PMDF applies address reversal to envelope From: addresses as well as header addresses. This option will have no effect if the USE_REVERSE_DATABASE option is set to 0 or if neither the reverse database nor a REVERSE mapping exist. The default is 1, which means that PMDF will attempt to apply any address reversal to envelope From: addresses. A value of 0 will disable this use of the address reversal database and REVERSE mapping.

SUPPRESS_CONTENT_DISP (integer 0, 1, or 2)

This option suppresses the addition of a Content-disposition header to a message or message part when PMDF parses out and re-assembles the MIME parts of a message. PMDF can be configured to do this in several ways, for example, by using the inner or innertrim channel keywords, or by using the CHARSET-CONVERSION mapping table.

Normally, when parsing the MIME part headers, if PMDF finds a name parameter in the Content-type header, it will add a Content-disposition header with a filename parameter. This appears to cause problems with messages generated by Outlook Calendar, with message parts that are of type text/calendar and do not have a Content-disposition header. The generation of this header by PMDF can be suppressed by specifing the SUPPRESS_CONTENT_DISP option. A value of 1 always suppresses the generation of a Content-disposition header, and a value of 2 suppresses the generation of the Content-disposition header only for text/calendar message parts.

USE_ALIAS_DATABASE (integer 0, 1, or 2)

The USE_ALIAS_DATABASE option controls whether and how PMDF makes use of the alias database as a source of system aliases for local addresses. A value of 0 disables use of the alias database. A value of 1, the default, causes PMDF to check the database if it exists. A value of 2 requires use the alias database. With this setting, if the database does not exist or is inaccessable for any other reason, all messages will be rejected with a temporary error.

USE_DOMAIN_DATABASE (0 or 1)

The USE_DOMAIN_DATABASE option controls whether or not PMDF makes use of the domain database as a source of rewrite rules. The default is 1, which means that PMDF will check the database if it exists. A value of 0 will disable this use of the domain database.

USE_FORWARD_DATABASE (integer)

The USE_FORWARD_DATABASE controls whether or not PMDF makes use of the forward database. 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, the forward database is used.
3 8 When set, channel-level granularity is used with the forward database entries. Forward database entries' left hand sides must have the form (note the vertical bars, |) 
source-channel|
from-address|
to-address
4 16 When set, channel-level granularity is used with the FORWARD mapping. FORWARD mapping entries' patterns (left hand sides) must have the form (note the vertical bars, |) 
source-channel|
from-address|
to-address
Bit 0 is the least significant bit.
The default value for USE_FORWARD_DATABASE is 0, which means that PMDF will not use the forward database at all. Note that a FORWARD mapping, if present, is always consulted.

USE_PERSONAL_ALIASES (0 or 1)

The USE_PERSONAL_ALIASES option controls whether or not PMDF makes use of personal alias databases as a source of aliases for local addresses. The default is 1, which means that PMDF will check such databases, if they exist. A value of 0 will disable personal aliases and make them unavailable to all users.

USE_REVERSE_DATABASE (0-511)

The USE_REVERSE_DATABASE option controls whether or not PMDF makes use of the address reversal database and REVERSE mapping as a source of substitution addresses. 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, address reversal is applied to addresses after they have been rewritten by the PMDF address rewriting process.
1 2 When set, address reversal is applied before addresses have had PMDF address rewriting applied to them.
2 4 When set, address reversal will be applied to all addresses, not just to backwards-pointing addresses.
3 8 When set, channel-level granularity is used with the REVERSE mapping. REVERSE mapping table (pattern) entries must have the form (note the vertical bars, |) 
source-channel|
destination-channel|
address
4 16 When set, channel-level granularity is used with address reversal database entries. Reversal database entries' left hand sides must have the form (note the vertical bars, |) 
source-channel|
destination-channel|
address
5 32 Apply REVERSE mapping even if a reverse database entry has already matched.
6 64 Apply address reversal to message ids.
7 128 When set, this modifies the effect of bit 4 (channel-level granularity of address reversal database entries); when this bit is also set, the address reversal database entries take the form (note the vertical bars, |) 
destination-channel|
address
8 256 When set, this modifies the effect of bit 3 (channel-level granularity of REVERSE mapping table entries); when this bit is also set, the REVERSE mapping table entries take the form (note the vertical bars, |) 
destination-channel|
address
Bit 0 is the least significant bit.
The default value for USE_REVERSE_DATABASE is 5, which means that PMDF will reverse Envelope From: addresses and both backwards and forwards pointing addresses after they have passed through the normal address rewriting process. Simple address strings are presented to both the REVERSE mapping and the reverse database. Note that a value of 0 disables the use of the address reversal completely. Note that the default of 5 represents a change from earlier versions of PMDF in which this option had a default value of 1 (reverse only backwards pointing addresses).

Previous Next Contents Index