This prevents several
kinds of mail loops. (Note that the SmartList program supports an X-Loop: header with the
same function.)
The Delivered-To: header should never be declared in the configuration file.
This is the Title of the Book, eMatter Edition
Copyright ?© 2007 O??™Reilly & Associates, Inc. All rights reserved.
1156 | Chapter 25: The H (Headers) Configuration Command
25.12.16 Disposition-Notification-To:
Final message disposition RFC2298
Even after a message is delivered to the final recipient, later recipient actions can alter the
eventual disposition of that message. The recipient can choose to delete the message
without reading it, read the message but not reply to it, forward the message, or do any
number of other things to it. The Disposition-Notification-To: header was devised as a
way to notify the sender about the ultimate disposition of the message. This header is advisory
only, not mandatory, and is used like this:
Disposition-Notification-To: 1#address
Here, the 1# is literal. The domain part of the address is compared to the domain part of
the address in the Return-Path: header (?§25.12.33 on page 1165), and if they differ, or if
the Return-Path: header is absent, no disposition notice is sent. If the two domains are the
same, and if the recipient allows the response, notification of the message disposition is
mailed back to the address using a special format.
Pages:
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082