Hank van Cleef wrote: > >However, I've also gotten about fifty other bounce disables on the 2.0 >score. Some investigation shows that affected users had accumulated >two bounces several months ago, but none since. From what I see in >the bounce logs still in my rotation, it appears that the bounce >processor did not sense that these bounces were very stale (over 90 >days, when I've specified 4), but simply operated on my reducing the >score from 3.0 to 2.0. A couple of users have forwarded back the >bounce e-mail they received and have noted the "last bounce dates" in >March-April. > >Mailman version is 2.1.9, local build with Python 2.4.3 on Solaris 9.
Fixed in 2.1.10. See <http://www.msapiro.net/scripts/reset_bounce.py> (mirrored at <http://fog.ccsf.edu/~msapiro/scripts/reset_bounce.py>) for a withlist script to do a mass re-enable by domain. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ 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
