BSMTP service conversions
The MTA'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
CHARSET-CONVERSION mapping such as:
CHARSET-CONVERSION in-chan=bsout_*;out-chan=*;convert yes in-chan=*;out-chan=bsin_*;convert yes
whether in the MTA mappings file in legacy configuration, or in Unified Configuration alternatively appearing as:
msconfig> show mapping:CHARSET-CONVERSION role.mapping:CHARSET-CONVERSION.rule = in-chan=bsout_*;out-chan=*;convert yes role.mapping:CHARSET-CONVERSION.rule = in-chan=*;out-chan=bsin_*;convert yes
Note that the
CHARSET-CONVERSION 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
CHARSET-CONVERSION 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
conversions file in legacy configuration. Section 19.2.3 provides examples of configuring specific service conversions on UNIX.