On 6/16/23 19:20, Mike Wertheim wrote:
I'm running an email list on mailman3.
My users are getting inundated by messages saying that their subscriptions have been disabled due to their bounce score exceeding the mailing list's bounce_score_threshold.
But there is nothing wrong with these users' email accounts. They are all perfectly fine. Apparently the issue is somehow related to spam.
Is spam being posted to your list? If so, you should ensure that Default action to take when a member posts to the list is set to Hold for moderation so that spammers can't subscribe to your list and post without the post being reviewed by a moderator. Then if the post is on topic, the moderator can set the user's moderation action to Default processing when accepting the post so subsequent posts won't be held.
Also set verp_probes: yes in the [mta] section of mailman.cfg. Then
when a user's score reaches threshhold, a probe message is sent and
delivery is only disabled if the probe bounces which it probably won't
if the issue is spam bounces.
Whenever I (as admin) get these emails, I just unsubscribe the user and then re-subscribe them. But also, the user gets confused and emails me about it, which unnecessarily takes up their time and mine.
That should be unnecessary. Just click on the member in the members list and set the member's Delivery status to Enabled. However, this may not work because of https://gitlab.com/mailman/mailman/-/issues/1061 which is not fixed until the next release, but enabling verp_probes will avoid that issue.
The relevant list settings are currently... bounce score threshold: 5 bounce info stale after: 7d bounce disabled warning interval: 7d bounce disable warnings: 5
What's the best way to fix this? I'm considering reducing "bounce info stale after" to "2d" and/or increasing "bounce disabled warning interval" to "90d".
Increasing "bounce disabled warning interval" or "bounce disable warnings" won't help because the user's delivery will still be disabled. It will just take longer for them to eventually be removed. Reducing "bounce info stale after" to "2d" might help as long as the list gets good posts more frequently than that, but the best way to deal with this is to enable verp_probes and then only consider other things if that doesn't help.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan