[Mailman-Users] Mailman 2.1.13 + vhost patches on multiple hosts

Guy wyldfury at gmail.com
Wed Feb 3 14:51:53 CET 2010

> Looking at the code I can find where the master-qrunner file is
> created in mailmanctl, but I'm not sure where the
> master-qrunner.<FQDN>.<numeric string> comes from so I didn't want to
> try making changes without some idea what's defining those file names.

Made a patch for Defaults.py.in that seems to have resolved that problem.

I've now run into two other problems.

1) The lists have their own vhost in apache lists.domain1.net with
ServerAlias lines for the other domains.
    http://lists.domain1.net/ gets this page:

Bug in Mailman version 2.1.13

We're sorry, we hit a bug!

Please inform the webmaster for this site of this problem. Printing of
traceback and other system information has been explicitly inhibited,
but the webmaster can find this information in the Mailman error logs.

I've run check_perms and it reported no problems. There's nothing in
the logs and no errors in the apache logs apart from a missing
favicon.ico file. Any suggestions on what else I should be looking at?

2) I've created a list from command line with
    newlist lists.domain2.net=test

aliases in /var/lib/mailman/data/ was updated fine. I then ran
genaliases and no virtual-mailman file was created. If I create the
virtual-mailman file with the same permissions as aliases and run
genaliases then virtual-mailman.db is created but virtual-mailman
itself remains empty. Do I need to filling virtual-mailman myself or
should genaliases be doing this? If genaliases should be doing it, any
suggests on why it's not doing so?

Don't just do something...sit there!

More information about the Mailman-Users mailing list