On 11/12/2014 19:12, Mark Sapiro wrote:
$ ls total 808 -rw-r--r-- 1 hal mailman 825894 Nov 8 15:39 my_list_name.mbox
And here's the problem.
sudo chmod g+w /var/lib/mailman/archives/private/my_list_name.mbox/my_list_name.mbox
will fix it. Then you can run bin/unshunt which will put the shunted messages in the archive, but as I said before, it's a good idea to first examine the contents of qfiles/shunt/ to be sure there aren't other messages there that you don't want requeued.
Got it! Thanks. The messages have entered the archive now and I'll keep a watch when new ones arrive to see if they're archived or bounced. So in summary, this is what I did:
- permission fixing for the archive
$ sudo chmod g+w /var/lib/mailman/archives/private/my_list_name.mbox/my_list_name.mbox
So this adds write permission to the group ("hal" and "mailman"), right? Here's a listing before issuing the above chmod command:
$ pwd /var/lib/mailman/archives/private/my_list_name.mbox $ ls total 808 -rw-r--r-- 1 hal mailman 825894 Nov 8 15:39 my_list_name.mbox $
..... then after doing "chmod g+w":
$ pwd /var/lib/mailman/archives/private/my_list_name.mbox $ ls total 860 -rw-rw-r-- 1 hal mailman 876548 Dec 12 23:22 my_list_name.mbox $
- Viewing the "error" Mailman logfile (to see what's wrong)
$ cd /var/log/mailman/ $ more error
- See what's inside the shunt directory and view their contents
(shunt=messages set aside instead of being archived) $ cd /var/spool/mailman/shunt/ $ ls $ /usr/lib/mailman/bin/show_qfiles /var/spool/mailman/shunt/*
- "Unshunt" messages
(put the set aside messages into the archive) $ /usr/lib/mailman/bin/unshunt
Hal