Notary decode MTA option

Notification message MTA options:  (-1, 0, or 1)
When the MTA is generating a DSN or MDN and using a    substitution sequence to insert original message headers into that DSN or MDN,  this option controls whether encoded-words (i.e., material in  character sets other than US-ASCII) present in the original message  header being inserted due to   are left alone, decoded if  already in the character set specified in the     file or    file being used, or forcibly converted to  the    character set or   character set and then decoded. (Note that the character set specified in the    file is the character set used for the first, human readable portion of  the DSN; the character set specified in the   file is the character set used for the first, human readable portion of the MDN.)

The default value is 0, meaning that encoded-words that match the character set specified in the   file or   file  will be decoded; encoded-words in other character sets will be left in  literal encoded form. A value of 1 causes encoded-words present in the original message header to be first converted to the character set  specified in the   or   file and then decoded;  that is, assuming that the character sets are all compatible, all  material will be converted and decoded and no encoded-words will be  left. A value of -1 disables decoding (and conversion) unconditionally; the original message headers are substituted literally, including the  encoded-words in their literal (MIME encoded) form.

Caution should be exercised in setting this option to a value of 1, as information loss  can occur, with resultant confusion, when a rich character set such as  UTF-8 is converted to a more limited character set (a character set  lacking many characters present in the original character set) such as  ISO-8859-1 or US-ASCII.

See also:
 * Notification message MTA options
 * Notification messages
 * The required full set of DSN type-specific return_...txt files
 * The disposition_...txt files
 * Notification message types