On 2018-03-25 17:58, Per Jessen wrote:

Carlos E. R. wrote:

...

On 2018-03-25 12:58, Per Jessen wrote:

...

Carlos E. R. wrote:

...

...

...

...

I did an update some hours ago, and after rebooting I noticed that posting did not work. I then saw this in the log, by the hundreds:

<2.4> 2018-03-24 00:57:56 Telcontar postfix 4336 - -  warning: process /usr/lib/postfix/bin//smtpd pid 17645 exit status 1 <2.4> 2018-03-24 00:57:56 Telcontar postfix 4336 - -  warning: /usr/lib/postfix/bin//smtpd: bad command startup -- throttling <2.2> 2018-03-24 00:58:16 Telcontar postfix 30967 - -  fatal: in parameter smtpd_relay_restrictions or smtpd_recipient_restrictions, specify at least one working instance of: reject_unauth_destination, defer_unauth_destination, reject, defer, defer_if_permit or check_relay_domains

I have not changed the config at all, so this must be some new default.

There is no "smtpd_relay_restrictions" in my main.cf. So the default setting will apply.

The default is empty:

Telcontar:~ # postconf smtpd_recipient_restrictions smtpd_recipient_restrictions =

FYI, you get the default postfix setting with '-d' :

postconf -d | grep _relay_

smtpd_relay_restrictions = permit_mynetworks, permit_sasl_authenticated, defer_unauth_destination

And here I get: smtpd_recipient_restrictions =

...

...

...

and it works. Comments?

Leap423 comes with postfix-3.2.0-1.4  - the vanilla install does indeed have "smtpd_recipient_restrictions = <blank>", but starts up fine. There is no update for postfix in Leap423.

I have "postfix-3.3.0-324.1.x86_64" from repo "Productivity/Networking/Email/Servers"

I have postfix and dovecot from that repo, perhaps Alpine too.

Then you're on your own I think.  Sounds like some configuration check was tightened sometime after 3.2.0.

It seems so. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)