Mark Sapiro wrote > >The mailman group does not have permission to create lock files in the >various /var/lib/mailman/archives/private/<listname>/database/ >directories. > >You said SELinux is off, so this must be a straight permissions issue.
I meant to add that all your missing archive messages are in /var/spool/mailman/shunt/. After you fix the permissions issue, you can reprocess them with Mailman's bin/unshunt. It is generally a good idea to look at the entries before unshunting all of them in case some are very old, irrelevant entries from before your migration. Given what must be the huge number of entries, this may be difficult, but I would look at those older than your migration with bin/show_qfiles to se if they should be removed befor running unshunt. Also, after you run bin/unshunt and the shunt queue is empty or nearly so, you might consider doing something like to reduce the physical size of the directory. Or you can simply do mv /var/spool/mailman/shunt /tmp/ cp -a /tmp/shunt /var/spool/mailman/ rm -r /tmp/shunt to reduce the physical size of the directory. -- 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://wiki.list.org/x/AgA3 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
