Non-MIME binary attachment conversion

Mail in certain non-standard (non-MIME) formats, e.g., mail in certain proprietary Sun formats or mail from the Microsoft® Mail  (MSMAIL) SMTP gateway, is automatically converted into MIME format if    is enabled for any of the channels involved in  handling the message. If you have a  channel, then it is  normally the incoming channel for messages from a Microsoft Mail SMTP  gateway, and the following will enable the conversion of messages  delivered to your local users: CHARSET-CONVERSION IN-CHAN=tcp_local;OUT-CHAN=ims-ms;CONVERT        Yes IN-CHAN=tcp_local;OUT-CHAN=tcp_lmtpcs&#x2a;;CONVERT   Yes You may also wish to add entries for channels to other local mail systems. For instance, an entry for the  channel: CHARSET-CONVERSION IN-CHAN=tcp_local;OUT-CHAN=ims-ms;CONVERT        Yes IN-CHAN=tcp_local;OUT-CHAN=tcp_lmtpcs&#x2a;;CONVERT   Yes IN-CHAN=tcp_local;OUT-CHAN=tcp_intranet;CONVERT  Yes Alternatively, to cover every channel you can simply specify. However, this may bring about an increase in message processing overhead as all  messages coming in the   channel will now be scrutinized  instead of just those bound to specific channels. (More importantly, such undiscriminated conversions may place your system in the dubious and frowned upon position of converting messages --- not necessarily your own site&#x27;s --- which are merely passing through your system, a situation in which you should merely be acting as a transport and not necessarily altering anything beyond the message envelope and related transport information.)

To convert MIME into the format Microsoft Mail SMTP gateway understands, use a separate channel in your MTA configuration for the  Microsoft Mail SMTP gateway, e.g., , and use  the following   mapping table entry: CHARSET-CONVERSION IN-CHAN=&#x2a;;OUT-CHAN=tcp_msmail;CONVERT       RFC1154

See also:
 * CHARSET-CONVERSION mapping table
 * Message reformatting