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 : VERP_README

PPoossttffiixx VVEERRPP HHoowwttoo

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

PPoossttffiixx VVEERRPP ssuuppppoorrtt

Postfix versions 1.1 and later support variable envelope return path addresses
on request. When VERP style delivery is requested, each recipient of a message
receives a customized copy of the message, with his/her own recipient address
encoded in the envelope sender address.

For example, when VERP style delivery is requested, Postfix delivers mail from
"owner-listname@origin" for a recipient "user@domain", with a sender address
that encodes the recipient as follows:

owner-listname+user=domain@origin

Thus, undeliverable mail can reveal the undeliverable recipient address without
requiring the list owner to parse bounce messages.

The VERP concept was popularized by the qmail MTA and by the ezmlm mailing list
manager. See http://cr.yp.to/proto/verp.txt for the ideas behind this concept.

Topics covered in this document:

* Postfix VERP configuration parameters
  * Using VERP with majordomo etc. mailing lists
  * VERP support in the Postfix SMTP server
  * VERP support in the Postfix sendmail command
  * VERP support in the Postfix QMQP server

PPoossttffiixx VVEERRPP ccoonnffiigguurraattiioonn ppaarraammeetteerrss

With Postfix, the whole process is controlled by four configuration parameters.

default_verp_delimiters (default value: +=)
    What VERP delimiter characters Postfix uses when VERP style delivery is
    requested but no explicit delimiters are specified.

verp_delimiter_filter (default: -+=)
    What characters Postfix accepts as VERP delimiter characters on the
    sendmail command line and in SMTP commands. Many characters must not be
    used as VERP delimiter characters, either because they already have a
    special meaning in email addresses (such as the @ or the %), because they
    are used as part of a username or domain name (such as alphanumerics), or
    because they are non-ASCII or control characters. And who knows, some
    characters may tickle bugs in vulnerable software, and we would not want
    that to happen.

smtpd_authorized_verp_clients (default value: none)
    What SMTP clients are allowed to request VERP style delivery. The Postfix
    QMQP server uses its own access control mechanism, and local submission
    (via /usr/sbin/sendmail etc.) is always authorized. To authorize a host,
    list its name, IP address, subnet (net/mask) or parent .domain.

With Postfix versions 1.1 and 2.0, this parameter is called
    authorized_verp_clients (default: $mynetworks).

disable_verp_bounces (default: no)
    if Postfix sends one bounce report for multi-recipient VERP mail, or one
    bounce report per recipient. The default, one per recipient, is what ezmlm
    needs.

UUssiinngg VVEERRPP wwiitthh mmaajjoorrddoommoo eettcc.. mmaaiilliinngg lliissttss

In order to make VERP useful with majordomo etc. mailing lists, you would
configure the list manager to submit mail according to one of the following two
forms:

Postfix 2.3 and later:

% sendmail -XV -f owner-listname other-arguments...

% sendmail -XV+= -f owner-listname other-arguments...

Postfix 2.2 and earlier (Postfix 2.3 understands the old syntax for backwards
compatibility, but will log a warning that reminds you of the new syntax):

% sendmail -V -f owner-listname other-arguments...

% sendmail -V+= -f owner-listname other-arguments...

The first form uses the default main.cf VERP delimiter characters. The second
form allows you to explicitly specify the VERP delimiter characters. The
example shows the recommended values.

This text assumes that you have set up an owner-listname alias that routes
undeliverable mail to a real person:

/etc/aliases:
        owner-listname: yourname+listname

In order to process bounces we are going to make extensive use of address
extension tricks.

You need to tell Postfix that + is the separator between an address and its
optional address extension, that address extensions are appended to .forward
file names, and that address extensions are to be discarded when doing alias
expansions:

/etc/postfix/main.cf:
        recipient_delimiter = +
        forward_path = $home/.forward${recipient_delimiter}${extension},
            $home/.forward
        propagate_unmatched_extensions = canonical, virtual

(the last two parameter settings are default settings).

You need to set up a file named .forward+listname with the commands that
process all the mail that is sent to the owner-listname address:

~/.forward+listname:
        "|/some/where/command ..."

With this set up, undeliverable mail for user@domain will be returned to the
following address:

owner-listname+user=domain@your.domain

which is processed by the command in your .forward+listname file. The message
should contain, among others, a To: header with the encapsulated recipient
sender address:

To: owner-listname+user=domain@your.domain

It is left as an exercise for the reader to parse the To: header line and to
pull out the user=domain part from the recipient address.

VVEERRPP ssuuppppoorrtt iinn tthhee PPoossttffiixx SSMMTTPP sseerrvveerr

The Postfix SMTP server implements a command XVERP to enable VERP style
delivery. The syntax allows two forms:

MAIL FROM:<sender@domain> XVERP

MAIL FROM:<sender@domain> XVERP=+=

The first form uses the default main.cf VERP delimiters, the second form
overrides them explicitly. The values shown are the recommended ones.

VVEERRPP ssuuppppoorrtt iinn tthhee PPoossttffiixx sseennddmmaaiill ccoommmmaanndd

The Postfix sendmail command has a -V flag to request VERP style delivery.
Specify one of the following two forms:

Postfix 2.3 and later:

% sendmail -XV -f owner-listname ....

% sendmail -XV+= -f owner-listname ....

Postfix 2.2 and earlier (Postfix 2.3 understands the old syntax for backwards
compatibility, but will log a warning that reminds you of the new syntax):

% sendmail -V -f owner-listname ....

% sendmail -V+= -f owner-listname ....

The first form uses the default main.cf VERP delimiters, the second form
overrides them explicitly. The values shown are the recommended ones.

VVEERRPP ssuuppppoorrtt iinn tthhee PPoossttffiixx QQMMQQPP sseerrvveerr

When the Postfix QMQP server receives mail with an envelope sender address of
the form:

listname-@your.domain-@[]

Postfix generates sender addresses "listname-user=domain@your.domain", using "-
=" as the VERP delimiters because qmail/ezmlm expect this.

More generally, a sender address of "prefix@origin-@[]" requests VERP style
delivery with sender addresses of the form "prefixuser=domain@origin". However,
Postfix allows only VERP delimiters that are specified with the
verp_delimiter_filter parameter. In particular, the "=" delimiter is required
for qmail compatibility (see the qmail addresses(5) manual page for details).

${this.title}

Code Editor : VERP_README