The work-around will still work, but is no longer necessary. In 2.1 you can set any list to automatically discard any held messages.
Many kudos to Barry and the development crew! This area of Mailman has been greatly expanded and improved - not only in choices, but in the robustness of the application. As an example of this, the request.db file can now simply be deleted and Mailman will recreate one as necessary. This make it quite easy to handle a run-away situation from the command line. Jon Carnes On Sat, 2003-02-01 at 11:17, Michael Ghens wrote: > Posts from non-members, I prefer to just delete and/or send a non-member > warning. I have just upgraded to 2.1. > > In 2.0.xx, I had to have a script running to delete posts and copy over a > db every day. > > Is this still the case? > > > ------------------------------------------------------ > 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/ > > This message was sent to: [EMAIL PROTECTED] > Unsubscribe or change your options at > http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com ------------------------------------------------------ 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/ This message was sent to: [email protected] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
