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.
