Mark Sapiro wrote: > >Because you lowered the threshold score. This is a known issue >mentioned several times on this list ><http://www.google.com/search?q=site%3Amail.python.org++inurl%3Amailman++cr >on+disabled+stale+bounce>
This does seem to be the same problem. >Are you sure you lowered the threshold a month ago? Has cron/disabled >not been running? The issue with cron/disabled disables that member >the first time cron/disabled runs after the threshold is lowered to <= >4. As best I can tell, cron/disabled has been running all this time. Issuing crontab -l generates output including: 0 9 * * * /usr/local/bin/python -S /home/godsgroups/mailman/cron/disabled Is there any way to know for sure if cron/disabled has been running? >Note: I'm going to fix cron/disabled for the 2.1.10 final release. Good to know. Thanks for that. David Buntin ------------------------------------------------------ Mailman-Users mailing list [email protected] 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
