CONVERSIONS mapping table

Although conversion processing is done using a regular MTA channel program, under normal circumstances this channel is never specified  directly either in an address or in an MTA  rewrite rule. Instead, the MTA controls routing to the conversion channel via the    mapping table.

In legacy configuration, the  mapping table (like all mapping tables), was stored in the   file. In Unified Configuration, the  mapping table is stored as the settings under either a   option or a   option. In Unified Configuration, most often creation or modification of such a  mapping table is performed using the   command of the   utility, to edit any or all  mapping tables in a format like the legacy   file; e.g.: msconfig&#x3e; edit mappings Or from within  the   mapping table can be created line-by-line: msconfig&#x3e; set mapping:CONVERSIONS.rule "IN-CHAN=tcp_local;OUT-CHAN=ims-ms;CONVERT" Yes msconfig# set mapping:CONVERSIONS.rule "IN-CHAN=ims-ms;OUT-CHAN=tcp_local;CONVERT" Yes msconfig# set mapping:CONVERSIONS.rule &#x2a; No Note that  mapping rules often include a special character such as the equal sign, , in either or both of the pattern (left hand side of the rule) or template (right hand side of the rule), thus often require quoting of pattern and/or template when being set at the   command line.

As the MTA processes each message it probes the   mapping (if  one is present) with a string of the default form IN-CHAN=source-channel;OUT-CHAN=destination-channel;CONVERT where   is the source channel from which the message is coming and    is the destination channel to  which the message is heading. New in MS 6.3, setting bit 1 (value 2) of the   MTA option  will  cause the probe to instead have the form IN-CHAN=source-channel;OUT-CHAN=destination-channel;TAG=tag-list;CONVERT where   is a comma-separated list of any conversion tags present on the message. Note that multiple conversion tags may be present; multiple tags will be included as a  comma-separated list. The total, combined length of such tags (that is, the length of the list, including the commas) is limited to 256 characters. (As with all mapping tables, the overall probe length is limited to 1024 characters.)

New in the 8.0 release, setting bit 6 (value 64) of the   MTA option will cause an additional, compound field to be appended to the    mapping table probe, immediately after any " " clause.

New in the 8.0.2.3 release, setting bit 0 (value 1) of the   MTA option will casue an additiona field to be appended to the    mapping table probe containing the destination domain for the current set of recipients, immediately after any " " and " " clauses.

If the probe matches the pattern (left hand side) of a   mapping table entry, then the resulting string (right hand side of the  mapping entry) should be a comma-separated list of keywords. Usually either just the keyword " " or  " " is specified. If " " is produced, the MTA will divert the  message from its regular destination to the conversion channel. (By also specifying , the message  can be diverted to some  alternate channel rather than to the regular conversion channel.)  If the message has a  conversion tag set, note that the "T"  flag will be set, and this can be tested for (when a match on the pattern, i.e., left hand side, occurred) using a    test in the template (right hand side) output string. If either " " is produced or no match is found, the message will be queued to the  regular destination channel.

Some less commonly used, additional template keywords, similar to those available for the    mapping table, are also available as shown below. 

For example, suppose messages coming in from the Internet and destined to the Message Store via either an    or    channel  require conversion processing. The following mapping would then be appropriate: CONVERSIONS IN-CHAN=tcp_local;OUT-CHAN=ims-ms;CONVERT         Yes IN-CHAN=tcp_local;OUT-CHAN=tcp_lmtpcs&#x2a;;CONVERT    Yes IN-CHAN=&#x2a;;OUT-CHAN=&#x2a;;CONVERT                      No In Unified Configuration,  &#x27;s   command could show the   mapping as above. Alternatively, msconfig&#x3e; show mapping:CONVERSIONS.&#x2a; role.mapping:CONVERSIONS.rule = IN-CHAN=tcp_local;OUT-CHAN=ims-ms;CONVERT Yes role.mapping:CONVERSIONS.rule = IN-CHAN=tcp_local;OUT-CHAN=tcp_lmtpcs&#x2a;;CONVERT Yes role.mapping:CONVERSIONS.rule = IN-CHAN=&#x2a;;OUT-CHAN=&#x2a;;CONVERT No

See also:
 * Conversion channel
 * original_channel_probe MTA Option
 * Alternate channel routing via the CONVERSIONS mapping
 * ims-ms channels
 * LMTP client TCPIP channels
 * CHARSET-CONVERSION mapping table
 * Character set conversion
 * MacMIME format conversions
 * thurman Option
 * include_conversiontag MTA Option
 * Conversion tags
 * include_mtpriority MTA Option
 * include_domain MTA Option