MDN language and customization

There are a number of localizable, customizable files the MTA consults when constructing MDNs; these files will be discussed further in  Customizing MDNs via the disposition files. By default, if no  mapping table is  configured, the   files located in the    directory will be used to generate  all MDNs. However, separate sets of   files can be created and  located in separate directories---for localization or site  customization purposes. Indeed, the MTA is distributed with several sets of langauge-specific   files, and a  basic   mapping table   (referenced in the mappings  file via file inclusion of the   file) which  selects among the language-specific directories based on language  preference of original message senders. That is, the   mapping table selects, based on any language  preference of the original message sender, a directory in which to find  an appropriate set of   files for generating  an MDN back to that sender.

Probes to the DISPOSITION_LANGUAGE mapping table have the form: mdn-type&#x7c;modifier&#x7c;source-channel&#x7c;accept-language&#x7c;return-address&#x7c;recipient where   can be any of ,  ,   ,  ,  , or   , and where   can be a  comma-separated list including any of  ,   ,  , or. The  field will have any values  (possibly a comma-separated list) found on (preferentially) an  Accept-Language: header line, or if that header line is not present  then from a Preferred-language: header line if present, or failing that  an X-Accept-Language: header line. Note that valid language tag values are discussed in RFC 3066 (Tags for the Identification of Languages).

The pattern (right hand side) of a  entry may set  the   flag to specify the directory from which the MTA  should use   files when constructing an MDN,  and optionally following a vertical bar character a destination  charset. The pattern may also optionally use the  flag  to set the Subject: field value to use when constructing this MDN; the  Subject: field follows yet another vertical bar character. (Note that the   Subject: will only be used if there is neither a  specific Subject: field for this type of MDN (such as a Sieve  " " might specify), nor a  SUBJECT option  set in the   file. That is, the    specified Subject: field value is of low precedence  compared to the other ways of setting the Subject: field value.) The  pattern may also optionally set the names of the files to use when  constructing this MDN instead of the normal  ,     , and    files; these are specified  following the directory specification but prior to the first vertical  bar character, with comma separators. All together, the syntax of the pattern is: $I$Tlangdir,option,prefix,mdn-type-file,suffix&#x7c;dest-charset&#x7c;subject See Sample NOTIFICATION_LANGUAGE and DISPOSITION_LANGUAGE mapping tables for an example   mapping table.

Note that as of MS 7.0.5,  all MDNs generated by the MTA include an  Auto-Submitted: header line, per the recommendation of  RFC 3834  (Recommendations for Automatic Responses to Electronic Mail) -- in  prior versions only certain forms of MDNs contained such a header line  -- and the value placed on the Auto-submitted: header line has been  updated to include the additional information suggested in  RFC 5436 (Sieve Notification Mechanism: mailto)  including additional values  (such as  ) and the    parameter.

See also:
 * Customizing MDNs via the disposition files
 * langdir MTA Option
 * NOTIFICATION_LANGUAGE and DISPOSITION_LANGUAGE sample mapping tables
 * Pre-defined mapping tables
 * Notification message format