Conversion control

From Messaging Server Technical Reference Wiki
Jump to: navigation, search

The actual conversions performed by the conversion channel are controlled by rules specified in the MTA conversions file (legacy configuration) or conversions MTA option (Unified Configuration). As of MS 7.0, the conversions file is (symbolically) IMTA_TABLE:conversions, i.e., CONFIGROOT/conversions. (In prior versions, the conversions file was located via the IMTA tailor file option imta_conversion_file, normally pointing to IMTA_TABLE:conversions.)

Note: Even in Unified Configuration, it is most convenient to think of the conversions option as a file, accessed and modified via the command


so from here on, references will be simply to "the conversions file", even for a Unified Configuration.

The MTA conversions file is a text file containing entries in a format that is modelled after MIME Content-type: parameters (see RFC 2045). Each entry consists of one or more lines grouped together; each line contains one or more "name=value;" parameter clauses. Quoting rules conform to MIME conventions for Content-type: header line parameters. Every line except the last must end with a semicolon. Entries are terminated by either a line that does not end in a semicolon, one or more blank lines, or both. For example, the following entry specifies that application/x-ddif parts in messages sent out to the Internet should be converted to PostScript:

out-chan=l; in-type=application; in-subtype=x-ddif; 
  out-type=application; out-subtype=postscript; parameter-copy-0=*; 
  command="ddifps $INPUT_FILE $OUTPUT_FILE" 

See also: