On 7/2/26 1:30 PM, Flo via Mailman-users wrote:
Other than myself not being familiar with this interface it looks to me that it doesn't meet my needs.
That may not be the case. It depends on why the user's mail is bouncing.
With verp probes enabled, when a user's bounce score reaches threshold, instead of disabling delivery, Mailman sends a probe message and only disables delivery if the probe bounces.
The idea is if the user's MTA is bouncing the mail because of spam filtering or something similar, the probe will hopefully not bounce.
There is another setting to disable attaching the bounce DSN to the probe in cast the bounce DSN itself contains things that cause the bounce. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.c...>.
I have a low volume list with is only used occasionally. If bounces are coming back on one occasion it should probe these addresses every other month four times. This means after eight months it should be removed, if no bounces appear anymore, it should be set back to normal.
What are your list settings for bounce processing? With a list that apparently only gets one post in a few months, the default settings
Bounce score threshold = 5 Bounce info stale after = 7d
will not disable delivery for any one as disabling would require 5 bounces with no more than 7 days between any two bounces.
For your above scenario, you might want something like
Bounce score threshold = 4 Bounce info stale after = 60d
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan