Hello,
Several days ago, I posted a message to his list concerning our installation of Mailman 2, and a weird problem that caused messages posted to a list to fail, as /usr/local/mailman/qfiles/in/ was behaving like it was read-only.
First off, thanks to everyone who replied with suggestions.
While we haven't determined what was causing this issue, we did devise a work-around of sorts. I'm posting it here in case someone else encounters the same issue.
The problem that we encountered was that mailman / python regarded /usr/local/mailman/qfiles and all the directories under it to be read-only. They're not - anything else that wants to create a file therein can do so.
This was how we fixed it:
- Stop mailman if it's running.
- cd /usr/local/mailman .
- cp -R qfiles /qfiles . (I suspect there are more appropriate places to copy the directory to, such as /var - this worked for us and we stopped messing with it.)
- mv qfiles qfiles.dist - just in case you ever figure out the real cause and want to reverse all this.
- ln -s /qfiles qfiles . (That is, create a symbolic link to the /qfiles directory, or wherever you decided to put it.)
- Start mailman
Mailman proved to have no problem writing to the relocated qfiles directory, and everything magically started working.
Hope this saves someone from banging their head against a wall, as we very nearly wound up doing.
::Jack