BSMTP service conversions

The MTA&#x27;s service conversion facility may be used with BSMTP channels to perform desired message transformations  on incoming and outgoing messages.

Usually outgoing BSMTP channels, BSOUT channels, are configured to perform one sort of service conversion on the messages they emit, and  incoming BSMTP channels, BSIN channels, are configured to perform the  inverse service conversion on messages they receive. Thus when BSMTP channels are used, the configuration would also usually contain a    mapping such as: CHARSET-CONVERSION in-chan=bsout_&#x2a;;out-chan=&#x2a;;convert     yes in-chan=&#x2a;;out-chan=bsin_&#x2a;;convert      yes whether in the MTA mappings file in legacy configuration, or in Unified Configuration alternatively appearing as: msconfig&#x3e; show mapping:CHARSET-CONVERSION role.mapping:CHARSET-CONVERSION.rule = in-chan=bsout_&#x2a;;out-chan=&#x2a;;convert yes role.mapping:CHARSET-CONVERSION.rule = in-chan=&#x2a;;out-chan=bsin_&#x2a;;convert yes Note that the  entries shown are such as to enable  service conversions for messages sent from BSOUT channels (such as  messages transitting through a BSOUT channel on their way out to an  outgoing TCP/IP channel), as well as for messages sent to a BSIN  channel (such as messages transitting through a BSIN channel on their  way in from an incoming TCP/IP channel).

Once execution of service conversions has been enabled via a   mapping such as that shown above, the specific  service conversions to be performed must be configured: whether as conversions entries in Unified Configuration, or   in the MTA    file in legacy configuration.

See also:
 * BSMTP channels
 * Service conversions
 * CHARSET-CONVERSION mapping table