PMDF System Manager's Guide

Although script channel processing is done using a regular PMDF channel program, under normal circumstances this channel is never specified directly either in an address or in a PMDF rewrite rule. PMDF controls access to the script channel via the SCRIPT mapping table in the PMDF mappings file.

As PMDF processes each message it probes the SCRIPT mapping (if one is present) with a string of the form

IN-CHAN=source-channel;OUT-CHAN=destination-channel;SCRIPT

where source-channel is the source channel from which the message is coming and destination-channel is the destination channel to which the message is heading. If a match occurs the resulting string should be a comma-separated list of keywords. Table 22-7 lists the available keywords.

Table 22-7 SCRIPT Mapping Table Keywords

Keyword	Action
Channel= channel	Enables script channel processing using the script channel named channel. Note that technically, the channel specified can be any channel defined in pmdf.cnf.
Maxblocks= n	Checks the size of the message. If it is larger than n blocks, then script channel processing is disabled, otherwise it is enabled.
Maxlines= n	Checks the number of lines in the message. If it is greater than n, then script channel processing is disabled, otherwise it is enabled.
No	Disables script channel processing.
Yes	Enables script channel processing.

A No is assumed if no match occurs.

If the SCRIPT mapping table enables the script channel, PMDF diverts the message from its regular destination to the script channel. If the script channel is not enabled, the message is queued to its regular destination channel.

For example, suppose messages require script processing if they come from outside your organization and are destined for either local users or remote MAIL-11 (DECnet) users. The following mapping would then be appropriate:

SCRIPT IN-CHAN=tcp_local;OUT-CHAN=l;SCRIPT Yes IN-CHAN=tcp_local;OUT-CHAN=d;SCRIPT Yes IN-CHAN=*;OUT-CHAN=*;SCRIPT No