Ivan Fetch wrote: > > I was planning to sync qfiles also (now that you mention it). Looking >at our current qfiles, some of them have files which look like they should >be deleted: > >Bounces: 260 (all .bak, but one .tmp)
There was a bug in 2.1.9 that would leave the .bak file behind when the runner encountered an "unparseable message" exception. You can examine these files with bin/dumpdb or bin/show_qfiles, but I think they're all spam and should be removed. >Shunt: 145 .pck > > Should I kill the files in bounces, and run unshunt on files in shunt >which are not terribly old? Again, look at the shunt queue entries with bin/dumpdb or bin/show_qfiles and delete all but the "good" ones. Also look in Mailman's error log for the corresponding time stamped entries to see what the underlying issue is. If it isn't fixed, the messages will just be shunted again. Once you have only "good" entries in the shunt queue, you can run unshunt. -- Mark Sapiro <[email protected]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
