Customizing DSNs via the return files

Customizing DSNs via the files
When the MTA needs to construct a notification message, the MTA will consult the     mapping table to find a language-appropriate set of    files. The MTA will then use that set of   files to construct the notification message. The   file  and (optional)     file are modifier files, potentially  affecting the spectrum of notification messages. The   files,  in contrast, are template files  for the different types of notification messages. Each such   file is used nearly verbatim for its  particular type(s) of notification messages, with possible  substitutions as specified via   substitutions. (The  MTA  option  controls this meaning of the percent character,  , in notification message 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,.

See also:
 * The sample header lines in DSNs: the return_header.opt file
 * The required full set of DSN type-specific return_...txt files
 * The optional return_option.opt file
 * MTA transaction log entry format
 * notices Option
 * Sieve language
 * Sieve capture extension
 * DSN language and customization