Gecko [ 122.154.134.11 ]

Name	Size	Permission
AAAREADME	2.7 KB	-rw-r--r--
ADDRESS_CLASS_README	9.33 KB	-rw-r--r--
ADDRESS_REWRITING_README	42.68 KB	-rw-r--r--
ADDRESS_VERIFICATION_README	19.46 KB	-rw-r--r--
BACKSCATTER_README	12.3 KB	-rw-r--r--
BASIC_CONFIGURATION_README	20.73 KB	-rw-r--r--
BUILTIN_FILTER_README	13.94 KB	-rw-r--r--
CDB_README	2.69 KB	-rw-r--r--
CONNECTION_CACHE_README	8.96 KB	-rw-r--r--
CONTENT_INSPECTION_README	3.29 KB	-rw-r--r--
DATABASE_README	13.25 KB	-rw-r--r--
DB_README	6.9 KB	-rw-r--r--
DEBUG_README	17.71 KB	-rw-r--r--
DSN_README	4.33 KB	-rw-r--r--
ETRN_README	11.4 KB	-rw-r--r--
FILTER_README	27.04 KB	-rw-r--r--
INSTALL	32.72 KB	-rw-r--r--
IPV6_README	11.73 KB	-rw-r--r--
LDAP_README	19.83 KB	-rw-r--r--
LINUX_README	1.64 KB	-rw-r--r--
LOCAL_RECIPIENT_README	5.65 KB	-rw-r--r--
MAILDROP_README	5.16 KB	-rw-r--r--
MILTER_README	36.6 KB	-rw-r--r--
MULTI_INSTANCE_README	42.4 KB	-rw-r--r--
MYSQL_README	4.31 KB	-rw-r--r--
NFS_README	4.73 KB	-rw-r--r--
OVERVIEW	18.57 KB	-rw-r--r--
PACKAGE_README	5.45 KB	-rw-r--r--
PCRE_README	2.87 KB	-rw-r--r--
PGSQL_README	4.4 KB	-rw-r--r--
QSHAPE_README	36.13 KB	-rw-r--r--
RELEASE_NOTES	12.37 KB	-rw-r--r--
RESTRICTION_CLASS_README	6.71 KB	-rw-r--r--
SASL_README	23.29 KB	-rw-r--r--
SCHEDULER_README	65.06 KB	-rw-r--r--
SMTPD_ACCESS_README	15.41 KB	-rw-r--r--
SMTPD_POLICY_README	19.37 KB	-rw-r--r--
SMTPD_PROXY_README	10.47 KB	-rw-r--r--
STANDARD_CONFIGURATION_README	25.24 KB	-rw-r--r--
STRESS_README	19.62 KB	-rw-r--r--
TLS_LEGACY_README	51.46 KB	-rw-r--r--
TLS_README	96.1 KB	-rw-r--r--
TUNING_README	23.76 KB	-rw-r--r--
ULTRIX_README	1.96 KB	-rw-r--r--
UUCP_README	5.14 KB	-rw-r--r--
VERP_README	7 KB	-rw-r--r--
VIRTUAL_README	23.29 KB	-rw-r--r--
XCLIENT_README	9.39 KB	-rw-r--r--
XFORWARD_README	8.28 KB	-rw-r--r--

Code Editor : DSN_README

PPoossttffiixx DDSSNN SSuuppppoorrtt

-------------------------------------------------------------------------------

IInnttrroodduuccttiioonn

Postfix version 2.3 introduces support for Delivery Status Notifications as
described in RFC 3464. This gives senders control over successful and failed
delivery notifications.

Specifically, DSN support gives an email sender the ability to specify:

* What notifications are sent: success, failure, delay, or none. Normally,
    Postfix informs the sender only when mail delivery is delayed or when
    delivery fails.

* What content is returned in case of failure: only the message headers, or
    the full message.

* An envelope ID that is returned as part of delivery status notifications.
    This identifies the message submission transaction, and must not be
    confused with the message ID, which identifies the message content.

The implementation of DSN support involves extra parameters to the SMTP MAIL
FROM and RCPT TO commands, as well as two Postfix sendmail command line options
that provide a sub-set of the functions of the extra SMTP command parameters.

This document has information on the following topics:

* Restricting the scope of "success" notifications
  * Postfix sendmail command-line interface
  * Postfix VERP support compatibility

RReessttrriiccttiinngg tthhee ssccooppee ooff ""ssuucccceessss"" nnoottiiffiiccaattiioonnss

Just like reports of undeliverable mail, DSN reports of successful delivery can
give away more information about the internal infrastructure than desirable.
Unfortunately, disallowing "success" notification requests requires disallowing
other DSN requests as well. The RFCs do not offer the option to negotiate
feature subsets.

This is not as bad as it sounds. When you turn off DSN for remote inbound mail,
remote senders with DSN support will still be informed that their mail reached
your Postfix gateway successfully; they just will not get successful delivery
notices from your internal systems. Remote senders lose very little: they can
no longer specify how Postfix should report delayed or failed delivery.

Use the smtpd_discard_ehlo_keyword_address_maps feature if you wish to allow
DSN requests from trusted clients but not from random strangers (see below for
how to turn this off for all clients):

/etc/postfix/main.cf:
        smtpd_discard_ehlo_keyword_address_maps =
            cidr:/etc/postfix/esmtp_access

/etc/postfix/esmtp_access:
        # Allow DSN requests from local subnet only
        192.168.0.0/28      silent-discard
        0.0.0.0/0           silent-discard, dsn
        ::/0                silent-discard, dsn

If you want to disallow all use of DSN requests from the network, use the
smtpd_discard_ehlo_keywords feature:

/etc/postfix/main.cf:
        smtpd_discard_ehlo_keywords = silent-discard, dsn

PPoossttffiixx sseennddmmaaiill ccoommmmaanndd--lliinnee iinntteerrffaaccee

Postfix has two Sendmail-compatible command-line options for DSN support.

* The first option specifies what notifications are sent for mail that is
    submitted via the Postfix sendmail(1) command line:

$ sseennddmmaaiill --NN ssuucccceessss,,ddeellaayy,,ffaaiilluurree ...... (one or more of these)
        $ sseennddmmaaiill --NN nneevveerr ......                 (or just this by itself)

The built-in default corresponds with "delay,failure".

* The second option specifies an envelope ID which is reported in delivery
    status notifications for mail that is submitted via the Postfix sendmail(1)
    command line:

$ sseennddmmaaiill --VV eennvveellooppee--iidd ......

Note: this conflicts with VERP support in older Postfix versions, as
    discussed in the next section.

PPoossttffiixx VVEERRPP ssuuppppoorrtt ccoommppaattiibbiilliittyy

With Postfix versions before 2.3, the sendmail(1) command uses the -V command-
line option to request VERP-style delivery. In order to request VERP style
delivery with Postfix 2.3 and later, you must specify -XV instead of -V.

The Postfix 2.3 sendmail(1) command will recognize if you try to use -V for
VERP-style delivery. It will do the right thing and will remind you of the new
syntax.

${this.title}

Code Editor : DSN_README