Well, I found http://www.mail-archive.com/mailman-developers@python.org/msg09827.html which rather explains this, and identifies it as a mailman bug.
Does anyone know if this has been addressed, or will be addressed in new versions of mailman? Thus spake Lindsay Haisley on Mon, Sep 18, 2006 at 03:11:15PM CDT > I just received a message via one of my list admins from a subscriber who was > unsubscribed from a list based on a bounce from last year. The subscriber > got > a message with the following: > > > Your membership in the mailing list ..... has been disabled > > due to excessive bounces The last bounce received from you was dated > > 12-Mar-2005. You will not get any more messages from this list until > > you re-enable your membership. > > Indeed, if I use dbdump to look at the config.pck for the list I see _many_ > entries such as the following: > > '[address_redacted]': <bounce info for member > [address_redacted] > current score: 2.0 > last bounce date: (2005, 2, 17) > email notices left: 3 > last notice date: (1970, 1, 1) > confirmation cookie: None > > > I notice two things about these. First, the last bounce date is _way_ in the > past, even though bounce_info_stale_after is set to 12 days. The second is > that the last notice date is bogus. Mailman _is_ resetting bounce > information > since I get many notices such as the following in my mailman logs: > > Sep 18 12:05:24 2006 (17300) listname: [address_redacted] has stale bounce > info, resetting > Sep 18 13:15:55 2006 (17300) listname: [address_redacted] has stale bounce > info, resetting > Sep 18 13:32:43 2006 (17300) listname: [address_redacted] has stale bounce > info, resetting > > ... so it looks as if bounce counts _are_ getting reset. > > This list has been ongoing for a long time, and the entire list was moved to > a > new server early this year and has been functioning normally otherwise. I > suspect that these database entries may have gotten crosswise of a mailman > version upgrade, of which there have been several since the list was moved to > mailman. > > Can anyone tell me how I can straighten this out and get the mechanics of > bounce processing working properly? > > -- > Lindsay Haisley | "Fighting against human | PGP public key > FMP Computer Services | creativity is like | available at > 512-259-1190 | trying to eradicate | <http://pubkeys.fmp.com> > http://www.fmp.com | dandelions" | > | (Pamela Jones) | > ------------------------------------------------------ > Mailman-Users mailing list > Mailman-Users@python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: > http://mail.python.org/mailman/options/mailman-users/fmouse-mailman%40fmp.com > > Security Policy: > http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp -- Lindsay Haisley | "Fighting against human | PGP public key FMP Computer Services | creativity is like | available at 512-259-1190 | trying to eradicate | <http://pubkeys.fmp.com> http://www.fmp.com | dandelions" | | (Pamela Jones) | ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp