PMDF System Manager's Guide

Although conversion 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 conversion channel via the CONVERSIONS mapping table in the PMDF mappings file.

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

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

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-1 lists the available keywords.

Table 22-1 CONVERSIONS Mapping Table Keywords

Keyword	Action
Channel= channel	Enables conversion channel processing using the conversion channel named channel. Note that technically, the channel specified can be any channel defined in pmdf.cnf.
No	Disables conversion channel processing.
Yes	Enables conversion channel processing.

A No is assumed if no match occurs.

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

For example, suppose messages require command channel 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:

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