The required full set of DSN type-specific return ...txt files

The required full set of DSN type-specific  files
Within a language-specific directory as selected via the   mapping table, each type of DSN should have its  own   file, to be used in  constructing the text in the human-readable first part of the DSN,  where the   in the file name is also the  value in the   probe. Each type of DSN also has a default Subject: header field value, shown in  Table of DSN types and their default Subject: field text, though  these values may be overridden either via the     mapping table as described in  DSN language and customization  or via the SUBJECT option  in the    file. Table of DSN types and their default Subject: field text lists the usage of each of these   files.

1New in MS 7.0u2.

2The Subject: field value can be overridden by setting a single value to be used for all DSNs via the SUBJECT option of. Alternatively, a more complex approach is to use the   flag in the     mapping table to set Subject: field values.

As a concrete example, the distributed English language set of   files will be presented here. The prefix, bounced,  capture,  deferred,  delayed,  delivered,  error,  failed,  forwarded,  timedout, and suffix files are the ones normally found in the directory located via the   MTA option, typically. The MTA is also distributed with sets of   files in other, language-specific directories  under. Note that regardless of what language is a site&#x27;s own "preferred" language, notifications may be generated by the  MTA in other languages, using the   files from  other language-specific directories, according to any expressed  language preference of the original message sender (who will  receive the DSN). That is, it is not a site&#x27;s own language preference, but rather the language preference of the DSN recipient -- who is  possibly a remote user---that matters most when it comes to DSN  language!

 Sample English language   file

Content-type: text/plain; charset=us-ascii Content-language: en-US This report relates to a message you sent with the following header fields: %H  Sample English language  file

Your message is being returned. It was forced to return by the postmaster. The recipient list for this message was: %R  Sample English language  file

Attached message captured in accordance with site policy.  Sample English language   file

This system has been unable to deliver your message to the following recipients: %R  Sample English language  file

Your message has been enqueued and undeliverable for %C %u%s to the following recipients: %R The mail system will continue to try to deliver your message for an additional %L %u%s.  Sample English language  file

Your message has been successfully delivered to the following recipients: %R  Sample English language  file

Processing errors occurred during delivery: %R Delivery processing continued in spite of these errors.  Sample English language  file

Your message cannot be delivered to the following recipients: %R  Sample English language  file

Your message has been successfully relayed to the recipients %R on a remote system that does not support the generation of successful delivery receipts. This does NOT mean that your message has actually been placed in the recipients&#x27; mailboxes; merely that it has passed through a part of the message transport infrastructure. In the event of a nondelivery you should expect to receive a nondelivery notification; in the event of successful delivery, however, you are unlikely to receive a positive confirmation of delivery.  Sample English language  file

Your message is being returned; it has been enqueued and undeliverable for %C %u%s to the following recipients: %R  Sample English language  file - normally empty

(Note: the  file is typically empty.)

See also:
 * langdir MTA Option
 * MTA transaction log entry format
 * Mailing lists
 * Sieve language
 * Sieve capture extension
 * return utility
 * DSN language and customization
 * Customizing DSNs via the return files