p!ranha?
Server IP : 103.169.32.36  /  Your IP : 216.73.217.13
Web Server : Apache
System : Linux web.dpmptsp 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64
User : apache ( 48)
PHP Version : 5.6.40
Disable Function : NONE
MySQL : ON  |  cURL : ON  |  WGET : ON  |  Perl : ON  |  Python : ON  |  Sudo : ON  |  Pkexec : ON
Directory :  /usr/share/doc/postfix-2.10.1/README_FILES/

Upload File :
Curr3nt_D!r [ Writeable ] D0cum3nt_r0Ot [ Writeable ]

 
Command :
Current File : /usr/share/doc/postfix-2.10.1/README_FILES/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)
    Send one bounce report for multi-recipient VERP mail, instead of 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.

You can use the smtpd_command_filter feature to append XVERP to SMTP commands
from legacy software. This requires Postfix 2.7 or later.

    /etc/postfix/main.cf:
        smtpd_command_filter = pcre:/etc/postfix/append_verp.pcre
        smtpd_authorized_verp_clients = $mynetworks

    /etc/postfix/append_verp.pcre:
        /^(MAIL FROM:<listname@example\.com>.*)/ $1 XVERP

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).

N4m3
5!z3
L45t M0d!f!3d
0wn3r / Gr0up
P3Rm!55!0n5
0pt!0n5
..
--
December 20 2023 04:36:26
0 / 0
0755
AAAREADME
2.814 KB
December 09 2011 18:44:41
0 / 0
0644
ADDRESS_CLASS_README
9.326 KB
March 25 2007 14:53:46
0 / 0
0644
ADDRESS_REWRITING_README
42.684 KB
February 10 2010 15:51:30
0 / 0
0644
ADDRESS_VERIFICATION_README
21.89 KB
October 01 2012 18:01:50
0 / 0
0644
BACKSCATTER_README
12.488 KB
March 22 2011 12:33:00
0 / 0
0644
BASIC_CONFIGURATION_README
20.91 KB
October 01 2011 00:52:01
0 / 0
0644
BUILTIN_FILTER_README
13.939 KB
April 04 2009 23:09:26
0 / 0
0644
CDB_README
2.69 KB
January 12 2008 02:31:35
0 / 0
0644
CONNECTION_CACHE_README
8.961 KB
January 08 2010 18:40:27
0 / 0
0644
CONTENT_INSPECTION_README
3.286 KB
May 15 2006 21:33:58
0 / 0
0644
DATABASE_README
14.47 KB
March 18 2012 15:38:48
0 / 0
0644
DB_README
7.583 KB
January 17 2012 20:00:27
0 / 0
0644
DEBUG_README
17.706 KB
October 14 2011 17:56:01
0 / 0
0644
DSN_README
4.327 KB
March 22 2007 19:25:31
0 / 0
0644
ETRN_README
11.404 KB
March 23 2007 18:49:17
0 / 0
0644
FILTER_README
28.608 KB
October 05 2012 20:07:10
0 / 0
0644
INSTALL
41.279 KB
February 06 2013 22:08:43
0 / 0
0644
IPV6_README
11.794 KB
August 02 2012 19:07:06
0 / 0
0644
LDAP_README
20.424 KB
December 02 2010 16:23:59
0 / 0
0644
LINUX_README
2.324 KB
October 11 2012 14:17:57
0 / 0
0644
LOCAL_RECIPIENT_README
5.648 KB
March 25 2007 17:36:06
0 / 0
0644
MAILDROP_README
5.229 KB
January 08 2010 15:39:54
0 / 0
0644
MEMCACHE_README
2.268 KB
January 19 2012 19:35:16
0 / 0
0644
MILTER_README
37.37 KB
August 17 2011 00:20:18
0 / 0
0644
MULTI_INSTANCE_README
42.503 KB
October 07 2012 12:55:45
0 / 0
0644
MYSQL_README
4.309 KB
January 12 2008 02:14:53
0 / 0
0644
NFS_README
4.733 KB
January 11 2009 01:57:07
0 / 0
0644
OVERVIEW
20.309 KB
April 16 2011 14:07:09
0 / 0
0644
PACKAGE_README
5.468 KB
June 23 2011 16:31:17
0 / 0
0644
PCRE_README
2.865 KB
January 12 2008 02:14:54
0 / 0
0644
PGSQL_README
4.397 KB
January 12 2008 02:14:54
0 / 0
0644
POSTSCREEN_README
35.901 KB
November 24 2012 22:48:31
0 / 0
0644
QSHAPE_README
36.626 KB
September 11 2010 13:40:05
0 / 0
0644
RELEASE_NOTES
9.819 KB
June 14 2013 13:09:41
0 / 0
0644
RESTRICTION_CLASS_README
6.975 KB
October 06 2012 23:56:29
0 / 0
0644
SASL_README
64.834 KB
November 12 2012 11:53:21
0 / 0
0644
SCHEDULER_README
65.416 KB
November 28 2011 00:38:03
0 / 0
0644
SMTPD_ACCESS_README
20.536 KB
October 07 2012 15:28:05
0 / 0
0644
SMTPD_POLICY_README
21.842 KB
September 30 2012 22:32:22
0 / 0
0644
SMTPD_PROXY_README
11.881 KB
October 05 2012 20:07:10
0 / 0
0644
SOHO_README
12.707 KB
November 12 2012 11:53:21
0 / 0
0644
SQLITE_README
2.161 KB
July 28 2010 14:32:14
0 / 0
0644
STANDARD_CONFIGURATION_README
26.562 KB
October 12 2012 18:12:58
0 / 0
0644
STRESS_README
19.496 KB
June 17 2012 20:28:21
0 / 0
0644
TLS_LEGACY_README
51.459 KB
April 17 2009 21:56:03
0 / 0
0644
TLS_README
92.463 KB
February 03 2013 18:18:08
0 / 0
0644
TUNING_README
24.053 KB
September 02 2012 23:46:23
0 / 0
0644
ULTRIX_README
1.955 KB
April 11 2004 21:05:34
0 / 0
0644
UUCP_README
5.142 KB
December 09 2004 00:07:13
0 / 0
0644
VERP_README
7.354 KB
October 01 2012 18:01:50
0 / 0
0644
VIRTUAL_README
23.517 KB
August 01 2012 22:38:30
0 / 0
0644
XCLIENT_README
9.507 KB
December 18 2011 22:59:48
0 / 0
0644
XFORWARD_README
8.572 KB
September 10 2010 20:40:22
0 / 0
0644