Customizing MDNs via the disposition files

Customizing MDNs via the files
When the MTA needs to construct an MDN, the MTA will consult the   mapping  table to find a language-appropriate set of    files, and optionally some override files  and values. The MTA will then use that set of   files, plus as relevant the    and   files  discussed in Customizing DSNs via the return files, to construct the MDN.

The  file,    file, and (optional)   files are  modifier files, potentially affecting the spectrum of MDN messages. The  files, in contrast, are template  files for the different types of MDNs. The   and    template files are used to "wrap"  the MDN-type-specific text;   each such      file  is used nearly  verbatim for its particular type(s) of MDN, with possible substitutions  as specified via   substitutions (defined from   ). (The  MTA  option  controls this meaning of the percent character,  , in MDN template files.) Note that in order to specify  inserting a literal percent character in a    file, the percent character must itself  be quoted with another percent character,. For the  substitution typically used in the   file (to insert header lines from the original message into the generated MDN), note that any decoding and/or character set conversion of any MIME-encoded, non-US-ASCII material in those original header lines is controlled by the   MTA option.

See also:
 * DISPOSITION_LANGUAGE mapping table
 * notary_quote MTA Option
 * notary_decode MTA Option
 * The disposition_...txt files
 * The disposition_option.opt file
 * Customizing DSNs via the return files
 * MDN language and customization