> We want for example these (different!) lists: > > [EMAIL PROTECTED] and [EMAIL PROTECTED] > > 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, [EMAIL PROTECTED] and [EMAIL PROTECTED] actually be called "host1" and "host2" in Mailman, but we have mail aliases that make [EMAIL PROTECTED] and [EMAIL PROTECTED] work, and the appropriate setting to let Mailman know that [EMAIL PROTECTED] and [EMAIL PROTECTED] 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 [EMAIL PROTECTED] and [EMAIL PROTECTED] work as expected (similarly for [EMAIL PROTECTED], 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 [EMAIL PROTECTED], 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 [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
