Am 16.01.2014 22:51, schrieb Wietse Venema:
> li...@rhsoft.net:
>>> There is no code in Postfix 2.11 that adds smtpd_relay_restrictions
>>> to main.cf
>>
>> it's the same code which added the safety-net in 2.10
>> "postfix upgrade-configuration"
>
> That safety net is commented out in Postfix 2.11, as I already
> mentioned. It now looks like this:
>
> # Disabled because unhelpful down-stream maintainers disable the safety net.
> # # Postfix 2.10.
> # # Safety net for incompatible changes due to the introduction
> # # of the smtpd_relay_restrictions feature to separate the
> # # mail relay policy from the spam blocking policy.
> # # PLEASE DO NOT REMOVE THIS CODE. ITS PURPOSE IS TO PREVENT
> # # INBOUND MAIL FROM UNEXPECTEDLY BOUNCING AFTER UPGRADING FROM
> # # POSTFIX BEFORE 2.10.
> # test -n "`$POSTCONF -c $config_directory -n smtpd_relay_restrictions`"
> || {
> # cat <<EOF | ${FMT}
> # COMPATIBILITY: editing $config_directory/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.
> #EOF
> # $POSTCONF -c $config_directory "smtpd_relay_restrictions = \
> # permit_mynetworks permit_sasl_authenticated \
> # defer_unauth_destination" || exit 1
> # }
>
> This safety net never added a SECOND smtpd_relay_restrictions line
> to main.cf, regardless of whether the '=' follows the parameter name
> on the same line or on a later line.
>
> I hope that we can now close this thread
since it affected only one of some machines i am Ok with this
for now production stays on 2.10.x and i will watch explicit for
this due upgrade them to 2.11.x later and compare "main.cf" before
and after
thanks for feedback!
