[Mailman-Developers] How to use real virtual hosting?

[Nathan Neulinger]

Actually, as long as you reasonably automate things, multiple
installations of mailman is not a big deal. What sucks rocks is having
to run multiple mailman controller processes simultaneously, when a
simple iterative queue processor would cover the needs of most sites.

There was a post on this list a while back on an unsupported way to do
that. I'd very much like to see this be a supported mechanism, via
something as simple as:

mailmanctl -s oneshot

Then, for sites that need that functionality of a non-ugly-hack virtual
hosting, they have a easy way to do this in a supported fashion - just
call mailmanctl -s oneshot for each installation of mailman in sequence
every X minutes, perhaps even running a few in parallel for extra
performance, but not running ALL of them at the same time.

-- Nathan

On Tue, 2003-03-18 at 18:45, Terri Oda wrote:
> > We want for example these (different!) lists:
> > 
> >   team1 at volleybalclub.dse.nl  and  team1 at soccerclub.dse.nl
> > 
> > The aliases needed for these mailing lists are stored in the same
> > alias file and so they cannot exist together.
> 
> On one of my servers, we solve this problem by having, say, list at host1 and
> list at host2 actually be called "host1" and "host2" in Mailman, but we have
> mail aliases that make list at host1 and list at host2 work, and the appropriate
> setting to let Mailman know that list at host1 and list at host2 are appropriate
> posting addresses for lists host1 and host2 respectively.
> 
> In our case, it's only the actual posting addresses where we want the same
> name, but it wouldn't be too hard to extend this to hide more than just the
> one address.
> 
> You could probably do something similar by naming your mailing lists
> team1_volleyball and team1_soccer and then setting up the appropriate
> mailing aliases so that team1 at volleyballclub.dse.nl and
> team1 at soccerclub.dse.nl work as expected (similarly for
> team1-request at volleyballclub.dse.nl, etc.)  If you don't like having the
> longer urls that'll result, you could also make
> http://volleybalclub.dse.nl/mailman/listinfo/team1 equivalent to
> http://volleybalclub.dse.nl/mailman/listinfo/team1_volleyball using
> mod_rewrite in Apache, or something similar for the webserver of your
> choice. 
> 
> It's a bit of a hack, though, since, of course, the list itself will still
> advertise addresses like team1_volleyball-request at volleyballclub.dse.nl, but
> it probably beats multiple installations of Mailman and it's fairly seamless
> to your users unless you forget to make some aliases. 
> 
>  Terri
> 
> 
> _______________________________________________
> Mailman-Developers mailing list
> Mailman-Developers at python.org
> http://mail.python.org/mailman/listinfo/mailman-developers
-- 

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul at umr.edu
University of Missouri - Rolla         Phone: (573) 341-4841
Computing Services                       Fax: (573) 341-4216