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

From Messaging Server Technical Reference Wiki
Jump to: navigation, search



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

Within a language-specific directory as selected via the NOTIFICATION_LANGUAGE mapping table, each type of DSN should have its own return_dsn-type.txt file, to be used in constructing the text in the human-readable first part of the DSN, where the dsn-type in the file name is also the value in the NOTIFICATION_LANGUAGE 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 NOTIFICATION_LANGUAGE mapping table as described in DSN language and customization or via the SUBJECT option in the return_option.opt file. Table of DSN types and their default Subject: field text lists the usage of each of these return_dsn-type.txt files.

DSN types and their default Subject: field text
Type of DSN Subject: field default text2 Usage
capture Message Capture Copy Used for the "capture" copy of a message captured due to Sieve script or LDAP attribute capture
bounced (security) Delivery Notification: Potential security problem found  
bounced (manual) Delivery Notification: Delivery has been manually aborted The message was manually returned due to the postmaster using a utility such as imsimta return or the imsimta qm utility's return command to bounce the message; this is one case of "R" MTA message transaction log entries
timedout Delivery Notification: Delivery has timed out and failed Used when generating a bounce message due to a message exceeding the final notices value; this is one case of "R" MTA message transaction log entries
failed Delivery Notification: Delivery has failed Recipient encountered a permanent delivery failure (a rejection); this is one case of "R" MTA message transaction log entries
deferred Delivery Notification: Delivery has been deferred Used when a notification is generated that a message that had a "Deliver on first try" notification request set encountered a temporary failure on that first attempt
delayed Delivery Notification: Delivery has been delayed Used when a warning notification is generated for a message that remains in the MTA's queues as yet undelivered: that is, this is the text used for warning messages generated at the non-final notices values, so corresponding to "W" MTA message transaction log entries
delivered Delivery Notification: Delivery has been successful Used when generating a delivery receipt for a message that had a NOTARY delivery receipt request
relayed Delivery Notification: Message successfully relayed Used when a message that had a NOTARY delivery receipt request is relayed onward to a host that does not support NOTARY
expanded Delivery Notification: Mailing list successfully expanded Used when an address that had a delivery receipt notification request is expanded into a mailing list; per NOTARY rules, such expansion is considered to be a successful "delivery" of the message (and the delivery receipt request does not get propagated/carried through to the message copies addressed to actual list members)
error Problem during delivery processing Used, for instance, for error reports to a Sieve "owner" regarding Sieve syntax problems
journal1 Message Journal Copy Used in messages captured with the Sieve capture action's :journal parameter

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 return_option.opt. Alternatively, a more complex approach is to use the $T flag in the NOTIFICATION_LANGUAGE mapping table to set Subject: field values.

As a concrete example, the distributed English language set of return_*.txt 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 langdir MTA option, typically IMTA_TABLE:locale/C. The MTA is also distributed with sets of return_*.txt files in other, language-specific directories under IMTA_ROOT:lib/locale. Note that regardless of what language is a site's own "preferred" language, notifications may be generated by the MTA in other languages, using the return_*.txt 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'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 return_prefix.txt 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 return_bounced.txt 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 return_capture.txt file



 
Attached message captured in accordance with site policy. 

Sample English language return_deferred.txt file



This system has been unable to deliver your message to the 
following recipients: 
%R 
 

Sample English language return_delayed.txt 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 return_delivered.txt file



Your message has been successfully delivered to the following recipients: 
%R 
 

Sample English language return_error.txt file



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

Sample English language return_failed.txt file



Your message cannot be delivered to the following recipients: 
%R 
 

Sample English language return_forwarded.txt 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' 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 return_timedout.txt file



Your message is being returned; it has been enqueued and undeliverable for 
%C %u%s to the following recipients: 
%R 

Sample English language return_suffix.txt file - normally empty



 

(Note: the return_suffix.txt file is typically empty.)


See also: