On Tue, 2003-10-21 at 05:40, javier wrote: > hello... > one of the ten lists i have working stoped sending messages,. Ok, at > moment i have to rmlist <blocked list>, saving the config file, and i > have to create the same new list again, with same config file, and > without removing archives... but... i don't know if i could solve this > problem better... > i can't find why the list stops sending messages, may the cron process > of sending digest is the reason, i've send a HELP message yesterday with > the output cron command. > > thank you very much
Javier, Look in the FAQ for Mailman (3.14) might be helpful. If you are not running the latest version of your Mailman branch, then you should consider upgrading: For 2.0. that would be 2.0.13 For 2.1 that would be 2.1.3 In general, check for a locking file problem first, then check the qfiles to see what is stuck in the queue. It may be that one of your users on that list has a do-it-yourself email program that is sending out corrupt headers. You should NEVER need to delete the existing list. If this solves the problem for you, then try running "check_perms -f" and see if that finds any problems. This will check the rights on most of the key files needed for Mailman to run properly. Good Luck - Jon Carnes ------------------------------------------------------ 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
