[Mailman-Users] Mailman stopped sending mail todayandstoppedarchiving a month ago

[Dan Mashal]

Thank you so much!! The archive dirs were owned by root. I chowned the
archive dirs and ran unshunt and now all my archives show up. I also
fixed the 2 outgoing copies of qrunner.

Unfortunately, Fedora has not come out with a yum mailman package for
2.10 or 2.11.. so I'm still waiting on this but it kinda scares me that
it might break something. 

Thank you again!

Dan

-----Original Message-----
From: Mark Sapiro [mailto:mark at msapiro.net] 
Sent: Tuesday, June 24, 2008 5:51 PM
To: Dan Mashal; mailman-users at python.org
Subject: Re: [Mailman-Users] Mailman stopped sending mail
todayandstoppedarchiving a month ago

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 <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan