On 5/28/21 11:32 AM, Bjoern Franke wrote:
But since the upgrade from 3.2.1 to 3.3.x the list owners are spammed with
some.listmember@domain.tld's subscription has been disabled on nordwest@lists.ffnw.de due to their bounce score exceeding the mailing list's bounce_score_threshold.
This should really be better documented (sigh)
Prior to Mailman 3.3.1, bounces were recorded but not processed. Beginning with Mailman 3.3.1, bounces are now properly processed. The issue is all those unprocessed bounces were still in the bounceevent table in the database and even though they were old and likely irrelevant, upon upgrade they were all processed resulting in many spurious disabling of delivery.
This is disruptive, but is a one time thing and in your case is now done.
For those who haven't yet upgraded, there are two ways to avoid this. The best way is before starting Mailman after upgrading, set
[mta]
verp_probes: yes
in mailman.cfg to enable bounce probes. With probes enabled, users whose score reaches threshold are sent a probe message and their delivery is only disabled if the probe bounces which will only happen for currently undeliverable addresses.
The other way is before starting Mailman after upgrading, run a database query similar to
UPDATE bounceevent SET processed = 1;
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan