There seems to be a small problem with Mailman confusing PREFIX with VAR_PREFIX at some point in the Mailman code. After upgrading to 2.1.9-r3 (and breaking and mostly fixing my customers' list installations) I got errors in my mail logs such as the following on attempted posts to lists: Mar 6 01:19:24 shakti courierlocal: id=000000000015F4AC.0000000047CF9AFC.00003BEB,from=<fmouse@fmp.com>,addr=<lupe@moco verde.org>: exceptions.OSError [Errno 2] No such file or directory: '/usr/lib64/mailman/lists' Mar 6 01:19:24 shakti courierlocal: id=000000000015F4AC.0000000047CF9AFC.00003BEB,from=<fmouse@fmp.com>,addr=<lupe@moco verde.org>: Line 112 Mar 6 01:19:24 shakti courierlocal: id=000000000015F4AC.0000000047CF9AFC.00003BEB,from=<fmouse@fmp.com>,addr=<lupe@moco verde.org>,status: deferred Line 112 in one of the Mailman files is apparently generating a python exception trying to access '/usr/lib64/mailman/lists'. This can be worked around with a symlink, which is what I've resorted to, but this shouldn't be necessary. Defaults.py correctly assigns PREFIX and VAR_PREFIX: PREFIX = '/usr/lib64/mailman' VAR_PREFIX = '/var/lib/mailman' ... and LIST_DATA_DIR = os.path.join(VAR_PREFIX, 'lists') Grepping for other possible code errors turns up nothing obvious, except for the bin/update script which declares that 'list_dir = os.path.join(mm_cfg.PREFIX, "lists")' which needs to be fixed, but should have no bearing on this bug. Other parts of Mailman correctly access files in VAR_PREFIX (logs, archives), so it's not obvious what's going on here.
I found the source of this problem as far as my installation is concerned - a mis-config in the courier-to-mailman.py script (a variation and update on qmail-to-mailman.py) so I'm closing this bug since courier-to-mailman.py isn't part of the standard Mailman distribution, nor is it provided with the Gentoo ebuild. In the process of working on this, I did find several files in ~mailman/bin which need to be updated to reflect the segregation of mutable data into the VAR_PREFIX directory. I'll post these as a separate report, with patches.
*** Bug 212547 has been marked as a duplicate of this bug. ***
