On 12/22/2014 03:57 PM, Mark Sapiro wrote:
If you still have questions about this, tell us what Mailman version this is, whether or not you are receiving bounce_notify_owner_on_disable notices (if it's Off, turn it On), how they correlate with the unsubscribes and whether the attached DSNs look like real bounces, and if you have access to Mailman's logs, what's in the 'bounce' log going back as far as you can.
I meant to add here that if you have command line access to your Mailman server, there is a script at <http://www.msapiro.net/scripts/get_bounce_info.py> that you can use to print the bounce information for members with bounces. It will print for example, for a member who hasn't yet reached threshold
<bounce info for member user1@example.com current score: 1.0 last bounce date: (2014, 12, 20) email notices left: 3 last notice date: (1970, 1, 1) confirmation cookie: None >
and for a member soon to be removed from a list with threshold = 3.0
<bounce info for member user2@example.com current score: 3.0 last bounce date: (2014, 12, 8) email notices left: 0 last notice date: (2014, 12, 22) confirmation cookie: a4233de11a0ac735d1582f4cfc1dc99377643c9e >
The 'cookie' is the token sent to the user in the warning notice that can be used by the user to reset her bouncing status and enable delivery.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan