Never mind, I have spotted the bug in the default install.
Tom
On 0, Tom Cook <tom.cook@adelaide.edu.au> wrote:
> Hi all,
>
> I'm attempting to install and configure mailman. So far what I have
> done is this:
>
> apt-get install mailman
>
> which I usually find to be a pretty good start for installing most
> things ;-)
>
> Most of the mailman documentation I can find talks about a mailman
> user, and a mailman group, and cron jobs owned by that user. The
> install doesn't seem to have created such users on my system: there
> is no mailman in /etc/passwd and:
>
> # for i in `awk -F ":" "{print $1;}" /etc/passwd` ; do crontab -u $i -l ; done
>
> does not show any users with any cron jobs at all.
>
> The script /usr/lib/mailman/bin/check_perms reports that all
> permissions are set correctly when I run it as root. I suspect that
> root is not the right user to run it as, but then I don't seem to have
> a mailman user that I could run it as. All of the mailman stuff seems
> to be owned by root.
>
> I can create a new list using the newlist command, and I get the
> informative email about the list OK, but when I try to subscribe to
> the list, using either the web or mail interface, I get messages like
> this:
>
> Aug 10 01:00:02 2002 qrunner(3520): Traceback (most recent call last):
> Aug 10 01:00:02 2002 qrunner(3520): File
> "/usr/lib/mailman/cron/qrunner", line 276, in ?
> Aug 10 01:00:02 2002 qrunner(3520): lock.lock(timeout=0.5)
> Aug 10 01:00:02 2002 qrunner(3520): File
> "/usr/lib/mailman/Mailman/LockFile.py", line 219, in lock
> Aug 10 01:00:02 2002 qrunner(3520): self.__write()
> Aug 10 01:00:02 2002 qrunner(3520): File
> "/usr/lib/mailman/Mailman/LockFile.py", line 350, in __write
> Aug 10 01:00:02 2002 qrunner(3520): fp = open(self.__tmpfname,
> 'w')
> Aug 10 01:00:02 2002 qrunner(3520): IOError : [Errno 13] Permission
> denied: '/var/lib/mailman/locks/qrunner.lock.pinky.3520'
>
> A quick bit of googling will show a number of people with this
> problem, but the only solutions I could find talked about having the
> cron jobs entered twice or something, and since I don't even have them
> once this seems a bit irrelevant.
>
> So is there some bit of documentation I am missing, or is this some
> undocumented setup magic that you need to know to use mailman, or is
> there something wrong with mailman or my system?
>
> Thanks
> Tom
--
Tom Cook
Information Technology Services, The University of Adelaide
Classifications of inanimate objects: Those that don't work, those that break down, and those that get lost.
Get my GPG public key: https://pinky.its.adelaide.edu.au/~tkcook/tom.cook-at-adelaide.edu.au
Attachment:
pgpoup5Bf_teZ.pgp
Description: PGP signature