transport:destination

> - # Postfix ≤ 2.6 default
> - address_verify_poll_count = 3
> - # Poor man's greylisting
>   address_verify_poll_count = 1
> --- 251,252 ----
> ***************
> *** 435,447 ****
>   
> - address_verify_sender_dependent_default_transport_maps
> - (default: $sender_dependent_default_transport_maps)

> - 
> -  Overrides the sender_dependent_default_transport_maps parameter
> - setting for address verification probes.  
> - 
> -  This feature is available in Postfix 2.7 and later.  
> - 
> - 
> - 
> - 
>   address_verify_sender_dependent_relayhost_maps
> --- 384,385 ----
> ***************
> *** 461,489 ****
>   
> - 
address_verify_sender_ttl
> - (default: 0s)

> - 
> -  The time between changes in the time-dependent portion of address
> - verification probe sender addresses. The time-dependent portion is
> - appended to the localpart of the address specified with the
> - address_verify_sender parameter. This feature is ignored when the
> - probe sender addresses is the null sender, i.e. the address_verify_sender
> - value is empty or <>. 
> - 
> -  Historically, the probe sender address was fixed. This has
> - caused such addresses to end up on spammer mailing lists, and has
> - resulted in wasted network and processing resources.  
> - 
> -  To enable time-dependent probe sender addresses, specify a
> - non-zero time value (an integral value plus an optional one-letter
> - suffix that specifies the time unit).  Specify a value of at least
> - several hours, to avoid problems with senders that use greylisting.
> - Avoid nice TTL values, to make the result less predictable.  Time
> - units are: s (seconds), m (minutes), h (hours), d (days), w (weeks).
> - 
> - 
> -  This feature is available in Postfix 2.9 and later.  
> - 
> - 
> - 

> - 
>   address_verify_service_name
> --- 399,400 ----
> ***************
> *** 695,697 ****
>    To get the behavior before Postfix version 2.2, specify
> ! "local_header_rewrite_clients = static:all". 
>   
> --- 606,608 ----
>    To get the behavior before Postfix version 2.2, specify
> ! "local_header_rewrite_clients = static:all". 
>   
> ***************
> *** 749,762 ****
>   
> - 
always_add_missing_headers
> - (default: no)

> - 
> -  Always add (Resent-) From:, To:, Date: or Message-ID: headers
> - when not present.  Postfix 2.6 and later add these headers only
> - when clients match the local_header_rewrite_clients parameter
> - setting.  Earlier Postfix versions always add these headers; this
> - may break DKIM signatures that cover non-existent headers. 
> - 
> - 
> - 

> - 
>   always_bcc
> --- 660,661 ----
> ***************
> *** 776,779 ****
>   To avoid mailer loops, automatic BCC recipients are not generated
> ! after Postfix forwards mail internally, or after Postfix generates
> ! mail itself. 
>   
> --- 675,678 ----
>   To avoid mailer loops, automatic BCC recipients are not generated
> ! for mail that Postfix forwards internally, nor for mail that Postfix
> ! generates itself. 
>   
> ***************
> *** 859,861 ****
>    To get the behavior before Postfix version 2.2, specify
> ! "local_header_rewrite_clients = static:all". 
>   
> --- 758,760 ----
>    To get the behavior before Postfix version 2.2, specify
> ! "local_header_rewrite_clients = static:all". 
>   
> ***************
> *** 896,898 ****
>    To get the behavior before Postfix version 2.2, specify
> ! "local_header_rewrite_clients = static:all". 
>   
> --- 795,797 ----
>    To get the behavior before Postfix version 2.2, specify
> ! "local_header_rewrite_clients = static:all". 
>   
> ***************
> *** 906,908 ****
>   How long the postkick(1) command waits for a request to enter the
> ! Postfix daemon process input buffer before giving up.
>   
> --- 805,807 ----
>   How long the postkick(1) command waits for a request to enter the
> ! server's input buffer before giving up.
>   
> ***************
> *** 922,924 ****
>   
authorized_flush_users
> ! (default: static:anyone)

>   
> --- 821,823 ----
>   
authorized_flush_users
> ! (default: static:anyone)

>   
> ***************
> *** 956,958 ****
>   
authorized_mailq_users
> ! (default: static:anyone)

>   
> --- 855,857 ----
>   
authorized_mailq_users
> ! (default: static:anyone)

>   
> ***************
> *** 990,992 ****
>   
authorized_submit_users
> ! (default: static:anyone)

>   
> --- 889,891 ----
>   
authorized_submit_users
> ! (default: static:anyone)

>   
> ***************
> *** 1021,1023 ****
>   > ! authorized_submit_users = !www, static:all
>   
> --- 920,922 ----
>   > ! authorized_submit_users = !www, static:all
>   
> ***************
> *** 1034,1036 ****
>   
> !  What remote SMTP clients are allowed to specify the XVERP command.
>   This command requests that mail be delivered one recipient at a
> --- 933,935 ----
>   
> ! 
 What SMTP clients are allowed to specify the XVERP command.
>   This command requests that mail be delivered one recipient at a
> ***************
> *** 1246,1252 ****
>   
 The maximal amount of original message text that is sent in a
> ! non-delivery notification. Specify a byte count.  A message is
> ! returned as either message/rfc822 (the complete original) or as
> ! text/rfc822-headers (the headers only).  With Postfix version 2.4
> ! and earlier, a message is always returned as message/rfc822 and is
> ! truncated when it exceeds the size limit.
>   
> --- 1145,1151 ----
>    The maximal amount of original message text that is sent in a
> ! non-delivery notification. Specify a byte count. With Postfix 2.4
> ! and later, a message is returned as either message/rfc822 (the
> ! complete original) or as text/rfc822-headers (the headers only).
> ! With earlier Postfix versions, a message is always returned as
> ! message/rfc822 and is truncated when it exceeds the size limit.
>   
> ***************
> *** 1293,1295 ****
>   
> ! Enable inter-operability with remote SMTP clients that implement an obsolete
>   version of the AUTH command (RFC 4954). Examples of such clients
> --- 1192,1194 ----
>   

> ! Enable inter-operability with SMTP clients that implement an obsolete
>   version of the AUTH command (RFC 4954). Examples of such clients
> ***************
> *** 1360,1362 ****
>   
 To get the behavior before Postfix version 2.2, specify
> ! "local_header_rewrite_clients = static:all". 
>   
> --- 1259,1261 ----
>    To get the behavior before Postfix version 2.2, specify
> ! "local_header_rewrite_clients = static:all". 
>   
> ***************
> *** 1537,1540 ****
>   
> -  This feature is available in Postfix 2.2 and later. 
> - 
>   
> --- 1436,1437 ----
> ***************
> *** 1568,1593 ****
>   
> !  After the message is queued, send the entire message to the
> ! specified transport:destination. The transport name
> ! specifies the first field of a mail delivery agent definition in
> ! master.cf; the syntax of the next-hop destination is described
> ! in the manual page of the corresponding delivery agent.  More
> ! information about external content filters is in the Postfix
> ! FILTER_README file.  
> ! 
> !  Notes: 
> ! 
> ! 
> ! 
> !   This setting has lower precedence than a FILTER action
> ! that is specified in an access(5), header_checks(5) or body_checks(5)
> ! table. 
> ! 
> ! 
  The meaning of an empty next-hop filter destination
> ! is version dependent.  Postfix 2.7 and later will use the recipient
> ! domain; earlier versions will use $myhostname.  Specify
> ! "default_filter_nexthop = $myhostname" for compatibility with Postfix
> ! 2.6 or earlier, or specify a content_filter value with an explicit
> ! next-hop destination.  
>   
> ! 
>   
> --- 1465,1477 ----
>   
> ! 
> ! The name of a mail delivery transport that filters mail after
> ! it is queued.
> ! 
>   
> ! 
> ! This parameter uses the same syntax as the right-hand side of a
> ! Postfix transport(5) table. This setting has a lower precedence
> ! than a content filter that is specified with an access(5) table or
> ! in a header_checks(5) or body_checks(5) table.
> ! 
>   
> ***************
> *** 1622,1656 ****
>   
> - 
daemon_table_open_error_is_fatal
> - (default: no)

> - 
> -  How a Postfix daemon process handles errors while opening lookup
> - tables: gradual degradation or immediate termination. 
> - 
> - 
> - 
> -   no  (default) 
   Gradual degradation: a
> - daemon process logs a message of type "error" and continues execution
> - with reduced functionality. Features that do not depend on the
> - unavailable table will work normally, while features that depend
> - on the table will result in a type "warning" message.  
 When
> - the notify_classes parameter value contains the "data" class, the
> - Postfix SMTP server and client will report transcripts of sessions
> - with an error because a table is unavailable.  
 
> - 
> -   yes  (historical behavior) 
   Immediate
> - termination: a daemon process logs a type "fatal" message and
> - terminates immediately.  This option reduces the number of possible
> - code paths through Postfix, and may therefore be slightly more
> - secure than the default.  
 
> - 
> - 
> - 
> -  For the sake of sanity, the number of type "error" messages is
> - limited to 13 over the lifetime of a daemon process. 
> - 
> -  This feature is available in Postfix 2.9 and later.  
> - 
> - 
> - 

> - 
>   daemon_timeout
> --- 1506,1507 ----
> ***************
> *** 1711,1713 ****
>   debug_peer_list = 127.0.0.1
> ! debug_peer_list = example.com
>