PMDF System Manager's Guide


Previous Contents Index

6.2.1 Selecting Traffic for Conversion Processing

Although conversion 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 the mapping produces a result it should either be the string "Yes" or "No". If "Yes" is produced, PMDF will divert the message from its regular destination to the conversion channel. If either "No" is produced or no match is found, the message will be queued to the regular destination channel.

For example, suppose messages coming from PMDF-MR destined for either local users or remote MAIL-11 users require conversion processing. The following mapping would then be appropriate:


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


Previous Next Contents Index