Michael Orlitzky: > On 2020-07-14 09:29, Michael Orlitzky wrote: > > It appears that the blacklist entry is superseded by the cache? > > > > ... > > > > Is that intentional? Fixable? Work-aroundable? > > > > For posterity: digging into the source led me to discover the > > postscreen_blacklist_action (default: ignore) > > parameter that was new to me. Setting it to "enforce" or "drop" makes > postscreen reject these connections.
This is documented, in http://www.postfix.org/POSTSCREEN_README.html "The postscreen_blacklist_action parameter specifies the action that is taken next." And that text links to http://www.postfix.org/postconf.5.html#postscreen_blacklist_action Wietse
