One mailman instance that I work with is running 2.1.2 on a linux 2.4.20-20.9 kernel.
Mail to a specific list is not getting delivered, but other lists on the same instance are being delivered fine. The error message one person got back when they tried to send a message to the list was: ==== start error message === Traceback (most recent call last): File "/usr/local/mailman/cron/senddigests", line 94, in ? main() File "/usr/local/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 232, in process url = save_attachment(mlist, part, dir) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 348, in save_attachment fnext = os.path.splitext(msg.get_filename(''))[1] File "/usr/local/mailman/pythonlib/email/Message.py", line 707, in get_filename return unicode(newvalue[2], newvalue[0]) TypeError: unicode() argument 2 must be string, not None ==== end error message === I read this message to the list that is dated January 2006: == Mailman sends messages in both regular and digest delivery. The digest processing is inserted in the middle of regular delivery if the messages accumulated to a preset amount. If there is a serious error in the digest processing, the regular delivery fails. Since the messages are accumulated already, arrival of following message triggers the digest processing again and also fail in the subsequent regular delivery. == It went on to say: == Therefore, the site administrator should check the qfiles/shunt directory and the logs/error file periodically. == The recommendation was to go to 2.1.7 of mailman. Well, I'd rather not do that with all the lists going right now. I'll need to do that later. I guess something bombed with the digestifying. We don't digest the specific list, so I tried turning that off on the list, but that didn't help any. I saw in the FAQ to try "unshunt", but that doesn't seemed to have unstick the log jam. There are quite a few files in the qfiles/shunt directory. Is there a command or a set of procedures that I can run to make the list start delivering mail again normally? Hal Huntley SRI International ------------------------------------------------------ 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