Loading ...
Sorry, an error occurred while loading the content.

291800Re: smtpd_relay_restrictions in 2.10.0

Expand Messages
  • Noel Jones
    Mar 6, 2013
    • 0 Attachment
      Hash: SHA1

      On 3/6/2013 4:19 AM, Reindl Harald wrote:
      > Am 06.03.2013 11:08, schrieb Nikolaos Milas:
      >> I had a postfix 2.9.4 and upgraded to 2.10.0 (on CentOS 6.3
      >> x86_64), building an RPM using Simon J. Mudd's SRPM (for
      >> v2.9.x). During installation, I got:
      >> warning: /etc/postfix/main.cf created as
      >> /etc/postfix/main.cf.rpmnew warning: /etc/postfix/master.cf
      >> created as /etc/postfix/master.cf.rpmnew COMPATIBILITY:
      >> editing /etc/postfix/main.cf, overriding
      >> smtpd_relay_restrictions to prevent inbound mail from
      >> unexpectedly bouncing. Specify an empty
      >> smtpd_relay_restrictions value to keep using
      >> smtpd_recipient_restrictions as before.
      >> So, I thought I should set: "smtpd_relay_restrictions = "
      > which would kill your server

      Kill seems the wrong word here.

      This is, in fact, one of the recommended choices for backward
      compatibility. This disables the new smtpd_relay_restrictions
      feature and causes postfix to behave exactly as before. Setting
      "smtpd_relay_restrictions = " is very unlikely to break an
      existing, working installation, but you lose the benefit of the
      new feature.

      See RELEASE_NOTES for details.

      >> but I already have:
      >> smtpd_relay_restrictions = permit_mynetworks
      >> permit_sasl_authenticated defer_unauth_destination

      This is the safety net added by the postfix upgrade procedure.
      See RELEASE_NOTES for details.

      >> So, is there something I should do? (Updated Postfix seems to
      >> be working fine.)

      If you have a "standard" setup, change the above
      defer_unauth_destination to reject_unauth_destination. If you
      have a complex relay policy already defined in
      smtpd_recipient_restrictions, then set smtpd_relay_restrictions
      empty. See RELEASE_NOTES for details.

      -- Noel Jones
      -----BEGIN PGP SIGNATURE-----
      Version: GnuPG v2.0.17 (MingW32)
      Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

      -----END PGP SIGNATURE-----
    • Show all 3 messages in this topic