[Mailman-Users] Upgrading and using with multiple domains

[Mark Sapiro]

On 11/26/2014 08:05 AM, Jon 1234 wrote:
> I currently have Mailman 2.1.14 installed in the website directory of a.com


What does this mean? Normally, Mailman is installed in it's own
directory or directories which are not in the space served by default by
the web server. Then Mailman's CGI wrappers are pointed to in the web
server config (in Apache, via ScriptAlias), and Mailman's public
archives are pointed to via an Alias or similar.

What exactly is the situation in your case?


> I would like to:
> 1. Upgrade it to 2.1.18-1.

OK


2. Have it outside the website directory.


Again, what does this mean?


3. Use it not only for a.com but also b.com (I will not need to have the
same list names for both domains).


Not a problem.


> If I were to install from scratch outside the websites' directories, I imagine it would be simple enough to get it to work for b.com. 
> But what would I need to do to get the a.com mailing list to start using the new Mailman installation?


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.


> (Would I just be able to move certain files across to reproduce the archive, etc?)


Yes., but I don't see why it would be necessary to install the upgraded
mailman in a different place. Just put an appropriate

add_virtualhost('b.com', 'b.com')

directive in mm_cfg.py and configure your web server and MTA for the
additional virtual host.


> I am sorry for asking such a basic question, and would be happy to be directed to the right FAQs on the subject(s).


You might start with the installation manual at
<http://www.list.org/mailman-install/index.html>.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan