Ashley M. Kirchner wrote: > Will Yardley wrote: > > we use a virtual hosting setup, so we actually make the "list-name": > > [EMAIL PROTECTED] > > > > even though aliases point: > > [EMAIL PROTECTED] to the actual list post.
> I take a different approach: > > - I create <list> just the way I want it named (for example: test) > > - Sendmail's virtusertable does the following translation: > [EMAIL PROTECTED] test-lists.domain.net [...] > - The Alias file takes care of the rest (lines wrapped): > ## [EMAIL PROTECTED] mailing list > ## created: 13-Dec-2000 root > test-lists.domain.net: \ > "|/home/mailman/lists.domain.net/mail/wrapper post test" > This allows me to have multiple 'test' lists across multiple domains, > on the same machine, all behaving as separate lists. (This also means > I have multiple MM installations.) hrmm that seems like an interesting way to do things. do you use an automated system to create each one? i think a variation on this might fit our needs pretty well (although a way to simply change the email address sent by mailman would, of course, be nicer :>) do you use symbolic links for commands and just create a new directory structure for the data directories and stuff? seems like having lots of full mailman installations might be a major headache when it comes time to upgrade (keep in mind that we have about 10-12k customers and are now starting to allow unlimited discussion lists on all plans)... -- Will Yardley input: william < @ hq . newdream . net . > ------------------------------------------------------ Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
