On 7/8/20 6:05 AM, David Krantz wrote:

To my surprise mailman core started by sending tens of mails and blocking the corresponding users for very old bounces. What is worse is that this happens every time I start mailman core. Now I have blocked (almost) all outgoing mail in postfix using a transport map which discards it but this is a temporary testing measure of course.

Sorry about that. Yes this is an issue when first upgrading from a prior version to 3.3.1, there are lots of old unprocessed bounce events which all of a sudden get processed. See below for solutions.

When I deploy this server into production, I do not want these recipients to be blocked as the old problems have been solved since very long. My plan is to reload the database from a newer backup anyway... Would it be enough to empty the bounce table (bounceevent) or is there anything else driving this behaviour? Or is there a better way to do this via the mailman shell? For me a "delete from bounceevent" seems a lot simpler than anything via the shell but there may be dependencies in the database.

You are on the right track. The "delete from bounceevent" is a perfectly acceptable solution. So is "update bounceevent set processed = true".

Another way to deal with this is to set

[mta] verp_probes: yes

in mailman.cfg. This will still send a lot of probe messages which may be undesirable, but if the probes don't bounce, the user's delivery won't be disabled.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan