[Mailman-Users] Admin getting bug on one list

[Mark Sapiro]

Bill Christensen wrote:

>At 3:24 PM -0700 9/29/08, Mark Sapiro wrote:
>>
>>
>>It looks like at least once, you had removed config.pck and Mailman had
>>fallen back to config.pck.last - this is where the config.pck.safety
>>came from.
>>
>>It actually appears that some saves of the list are succeeding and that
>>maybe it is only the admin CGI that's failing.
>>
>>Does the list appear to work otherwise?
>
>Yes, mail from approved senders is going through.  This is a 
>moderated list though, so there are a number of messages stacked up 
>waiting for admin approval.
>
>>
>>What does
>>
>>  ls -ld /usr/local/mailman/lists/aen
>>
>>give: the permissions should be drwxrwsr-x and the group should be
>>mailman. The owner is normally root or the web server (nobody?)
>>depending on how the list was created.
>
>Yes, it's drwxrwsr-x and the owner and group match all the other 
>(working) lists


Is this Mac OS X? If so, see
<http://mail.python.org/pipermail/mailman-users/2005-January/042256.html>.

Unfortunately, the links in that post are all invalid. They should be

<http://mail.python.org/pipermail/mailman-users/2004-August/038697.html>

<http://mail.python.org/pipermail/mailman-users/2005-January/041638.html>

<http://mail.python.org/pipermail/mailman-users/2005-January/041650.html>

<http://mail.python.org/pipermail/mailman-users/2004-July/038384.html>

and the FAQ at <http://wiki.list.org/x/O4A9>.

The post at
<http://mail.python.org/pipermail/mailman-users/2004-July/038384.html>
indicates that that poster's problem was solved by simply removing
config.pck.last. It is OK to do that as long as there is a good
config.pck. If you're unsure, you could try just renaming
config.pck.last. The key is that there be no config.pck.last when you
go to the admindb page.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan