On 10/26/21 8:18 AM, Seth Seeger wrote:
I have just upgraded to 3.3.4 from 3.3.2 (via docker).
Do we need to do anything more than reset the delivery status? I am getting (seemingly) continual emails about bounces. I keep running the recipe in the link which resets everyone's delivery status. I've grep'd one member's address out of bounce.log (see below my signature).
Is it just catching up on old bounces?
There is no significant change in bounce processing from 3.3.2 to 3.3.4
If you really upgraded from 3.3.2, I don't know what would be responsible. On the other hand, it looks like you may in fact have upgraded from Mailman < 3.3.1 in which case, those are old, previously unprocessed bounces, and your log certainly looks like that.
If you think some or all users shouldn't have had delivery disabled, you can run the mailman shell seccion in the post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/... to re-enable them and let current bounce processing handle the truly undeliverable ones.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan