[Mailman-Users] Upgrading and using with multiple domains
mark at msapiro.net
Thu Nov 27 21:06:46 CET 2014
On 11/27/2014 02:39 AM, Jon 1234 wrote:
>> Date: Wed, 26 Nov 2014 21:01:36 -0800
>> From: mark at msapiro.net
>> What exactly is the situation in your case?
> At the very beginning I wrongly installed the files in a.com/mailman
> So the aliases are:
> ScriptAlias /mailman/ /path/a_com/mailman/cgi-bin/
> Alias /pipermail/ /path/a_com/archives/public/
> It works fine but I know this is not ideal. So I want to install Mailman where it should be: at /path instead of /path/a_com
>> Change the ScriptAlias and Alias or whatever they are in the web server
>> config to point to the correct place. Change the aliases or whatever is
>> used by the MTA that delivers a.com's mail to Mailman to deliver by
>> piping to the right wrapper.
> Fortunately this is what I did. Last night I typed up the necessary changes (mostly removing a_com/ from everything). The hosting company need to make the changes so I don't know yet if it works.
>> add_virtualhost('b.com', 'b.com')
>> directive in mm_cfg.py and configure your web server and MTA for the
>> additional virtual host.
> Again, this is what I did for b.com:
> add_virtualhost('www.b.com', 'b.com')
> and I am waiting to see if it works once the hosting company implement the changes.
> But seeing as I *do* now have two Mailman installations currently, I copied across the following directories from /path/a_com/mailman to /path/mailman
> I've asked the hosting company to run bin/mailmanctl stop on the existing installation before making the changes.
> I've added a .htaccess file to block web access for now in the a_com/mailman directory, just to cover the changeover.
> Is there anything else I ought to do?
Yes. Completely uninstall the a.com/mailman instance including any cron
jobs that run a.com/mailman/cron.* scripts.
> Will having installed Mailman twice have caused any confusion/conflicts in how the two installations work?
Yes. You will get password reminders and moderator request waiting
messages sent from the old installation. See, e.g., the FAQ at
> The only change I made to the standard installation was to make "mailman2" the site-wide list and add this to mm_cfg.py:
> MAILMAN_SITE_LIST = 'mailman2'
> To be honest, I'm not even sure that was necessary. Could I just have copied across the "mailman" files (as above) and not created the "mailman2" list? (Since, once the new installation works, I'll just delete the old one anyway.)
Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
More information about the Mailman-Users