Conversion channel definition

A conversion channel must be present in the MTA&#x27;s configuration in order for conversions to be performed. In Unified Configuration, a conversion channel is configured automatically, while in legacy configuration the post-installation configuration step normally caused an appropriate conversion channel  definition to be included in the MTA configuration file. The channel definition should have the general form: conversion CONVERSION-DAEMON or as displayed in Unified Configuration: msconfig&#x3e; show channel:conversion.&#x2a; role.channel.conversion.official_host_name = conversion-daemon As of MS 8.0, use of the   channel option is  recommended: conversion receivedstate "content" CONVERSION-DAEMON or in Unified Configuration: msconfig&#x3e; set channel:conversion.receivedstate content  Rewrite rules can be added if desired to make it possible to queue mail explicitly to the conversion channel. Something like conversion               $U%conversion.localhostname@conversion-daemon conversion.localhostname $U%conversion.localhostname@conversion-daemon where   is the name of this MTA system, will provide the necessary functionality. Note that in Unified Configuration, such rewrite rules would typically be automatically generated, and make use of the    and   and    substitutions,  to appear as: msconfig&#x3e; show rewrite.rule &#x2a; &#x2a;conversion&#x2a; role.rewrite.rule = conversion $U%conversion.domain.com@conversion-daemon role.rewrite.rule = conversion.&/IMTA_HOST/ $U%conversion.domain.com@conversion-daemon Once such rewrite rules are present, then addresses of the form user%host@conversion.localhostname will be routed through the conversion channel regardless of what the   mapping  table says.

See also:
 * receivedstate Option
 * CONVERSIONS mapping table
 * Conversion channel