that sounds good for me.. it shouldn't be a big effort to keep list names not colliding between domains.
however, how do you avoid the list administrator from changing the list preferred domain in the web interface?
-----Original Message----- From: mailman-users-admin@python.org [mailto:mailman-users-admin@python.org]On Behalf Of alex wetmore Sent: sabado, 16 de Junho de 2001 0:07 To: Rodrigo Borges Pereira Cc: mailman-users@python.org Subject: Re: [Mailman-Users] virtual hosting tactic
On Fri, 15 Jun 2001, Rodrigo Borges Pereira wrote:
I'm running a server that hosts a few domains. I already have mailman running for lists.mydomain.com, and it is working great.
However, now i want to give users that host domains the ability to use lists.userdomain.com too, and each user has it's own mailman setup under his domain.
If the lists don't have conflicting names then you can just set the "preferred domain" for each list to be the userdomain. As an example http://phred.org/mailman/listinfo, http://bikelist.org/mailman/listinfo, and http://cascade.bikelist.org/mailman/listinfo all point to lists on my servers, but act as if they are unique domains. You can send a message to any of the lists using any of the domains (ie, if there is a list xxx@cascade.bikelist.org you could get to it by sending email to xxx@phred.org), but I don't advertise that fact and users generally don't figure it out.
If you have conflicting list names then things get more complicated and you need to setup a mailman install per domain. There is a lot of information on this in the archives.
alex
Mailman-Users maillist - Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users