Package: postfix
Version: 2.10.0-1
Followup-For: Bug #702374

postfix 2.10 release notes states :

> Major changes - relay safety
> ----------------------------
> 
> [Incompat 20121007] As part of a forward compatibility safety net,
> the Postfix installation procedure adds the following
> smtpd_relay_restrictions entry to main.cf when there is none:
> 
>     smtpd_relay_restrictions = 
>     permit_mynetworks 
>     permit_sasl_authenticated 
>     defer_unauth_destination
> 
> If your site has a complex mail relay policy configured under
> smtpd_recipient_restrictions, this safety net will defer mail that
> the built-in smtpd_relay_restrictions setting would bounce. 
> 
> To eliminate this safety net, take one of the following three
> actions:
> 
> - Set smtpd_relay_restrictions empty, and keep using the existing
>   mail relay authorization policy in smtpd_recipient_restrictions.
> 
> - Copy the existing mail relay authorization policy from
>   smtpd_recipient_restrictions to smtpd_relay_restrictions.
> 
> - Set smtpd_relay_restrictions by hand to the new built-in
>   policy: permit_mynetworks reject_unauth_destination.
> 
> There is no need to change the value of smtpd_recipient_restrictions.
> 
> [Feature 20121007] This version introduces the smtpd_relay_restrictions
> feature for mail relay control. The new built-in default settings
> are:
> 
>     smtpd_relay_restrictions = 
>     permit_mynetworks 
>     reject_unauth_destination
> 
>     smtpd_recipient_restrictions =
>     ( optional spam blocking rules would go here )
> 
> For comparison, this is the Postfix before 2.10 default:
> 
>     smtpd_recipient_restrictions =
>     permit_mynetworks 
>     reject_unauth_destination
>     ( optional spam blocking rules would go here )
> 
> With Postfix versions before 2.10, the mail relay policy and spam
> blocking policy were combined under smtpd_recipient_restrictions,
> resulting in error-prone configuration.
> 
> As of Postfix 2.10, the mail relay policy is preferably implemented
> with smtpd_relay_restrictions, so that a permissive spam blocking
> policy under smtpd_recipient_restrictions will not unexpectedly
> result in a permissive mail relay policy.
> 
> As usual, this new feature is introduced with safety nets to prevent
> surprises when a site upgrades from an earlier Postfix release.
> 
> 1 - FORWARD COMPATIBILITY SAFETY NET: the Postfix installation
>     procedure adds the following smtpd_relay_restrictions entry to
>     main.cf when there is none:
> 
>     smtpd_relay_restrictions = 
>     permit_mynetworks 
>     permit_sasl_authenticated 
>     defer_unauth_destination
> 
>     If your site has a complex mail relay policy configured under
>     smtpd_recipient_restrictions, this safety net will defer mail
>     that the built-in smtpd_relay_restrictions setting would bounce.
> 
>     To eliminate this safety net, take one of the following three
>     actions:
> 
>     - Set smtpd_relay_restrictions empty, and keep using the existing
>       mail relay authorization policy in smtpd_recipient_restrictions.
> 
>     - Copy the existing mail relay authorization policy from
>       smtpd_recipient_restrictions to smtpd_relay_restrictions.
> 
>     - Set smtpd_relay_restrictions by hand to the new built-in
>       policy: permit_mynetworks reject_unauth_destination.
> 
>     There is no need to change the value of smtpd_recipient_restrictions.
> 
> 2 - BACKWARDS COMPATIBILITY SAFETY NET: sites that migrate from
>     Postfix versions before 2.10 can set smtpd_relay_restrictions
>     to the empty value, and use smtpd_recipient_restrictions exactly
>     as they used it before.
> 

upgrade of debian package does not add this smtpd_relay_restrictions


-- System Information:
Debian Release: 7.0
  APT prefers testing-proposed-updates
  APT policy: (900, 'testing-proposed-updates'), (900, 'testing'), (800, 
'stable'), (400, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages postfix depends on:
ii  adduser                3.113+nmu3
ii  cpio                   2.11+dfsg-0.1
ii  debconf [debconf-2.0]  1.5.49
ii  dpkg                   1.16.9
ii  libc6                  2.13-38
ii  libdb5.1               5.1.29-5
ii  libsasl2-2             2.1.25.dfsg1-6
ii  libsqlite3-0           3.7.13-1
ii  libssl1.0.0            1.0.1e-1
ii  lsb-base               4.1+Debian8
ii  netbase                5.0
ii  ssl-cert               1.0.32

Versions of packages postfix recommends:
ii  python  2.7.3-4

Versions of packages postfix suggests:
ii  bsd-mailx [mail-reader]        8.1.2-0.20111106cvs-1
ii  dovecot-common                 1:2.1.7-7
ii  dovecot-core [dovecot-common]  1:2.1.7-7
ii  emacs23-lucid [mail-reader]    23.4+1-4
ii  heirloom-mailx [mail-reader]   12.5-2
ii  libsasl2-modules               2.1.25.dfsg1-6
ii  mutt [mail-reader]             1.5.21-6.2
pn  postfix-cdb                    <none>
pn  postfix-doc                    <none>
ii  postfix-ldap                   2.10.0-1
pn  postfix-mysql                  <none>
ii  postfix-pcre                   2.10.0-1
pn  postfix-pgsql                  <none>
ii  procmail                       3.22-20
pn  resolvconf                     <none>
pn  sasl2-bin                      <none>
pn  ufw                            <none>

-- debconf information excluded


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to