Duncan Drury wrote: > >Any chance of releasing a patched version of mailman as promised a while >back? Not everyone using Mailman will be up to patching or manually editing >the code, and like a I said - for me at least this bug was a showstopper - >and a nasty one because it was pretty silent. Had I not been setting up a >new list, I may not have realised there was a problem for many months during >which no new subscriptions would have been happening on my lists.
The issue of a 2.1.10 patch release has become a bit complicated. There are a few other minor changes, and a new cron I have implemented to cull old entries from the bad and shunt queues. This goes a bit beyond a patch release. I have just returned from a vacation and am still trying to catch up, but my plan is to release what may be thought of as a 2.1.10 patch release, but to call it 2.1.11. This should happen before the end of this month. Regarding 'silent' problems - consider running Brad Knowles' daily status report (mmdsr). You will find this in the contrib directory in the unpacked tarball. It will report errors like this. -- 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