[Mailman-Users] List on a different domain name?

[Chris Arnold]

CA scratched his head and then wrote:

>We have 2 domains that i want to use with mailman, firstdomain.com and seconddomain.net. Should i have lists.firstdomain.com and lists.seconddomain.net?


>Let's say you want the web interfaces at lists.firstdomain.com and
lists.seconddomain.net respectively and the list email addresses to be
like list1 at firstdomain.com and list2 at seconddomain.net respectively.

>Let's further assume that there will be more lists in the
firstdomain.com domain.

>Then you would have

>DEFAULT_URL_HOST = 'lists.firstdomain.com'
>DEFAULT_EMAIL_HOST = 'firstdomain.com'
>VIRTUAL_HOSTS.clear()
>add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
>add_virtualhost('lists.seconddomain.net', 'seconddomain.net')
This use to work on a domain we had that has expired now and in fact when internal network users goto that old address, we can still use the old existing list. So i am not sure about the downstream and upstream packages you referred to.
I have tried everything you have suggested and nothing seems to work. You helped me get the old expired domain list working and i seem to remember something about split lists or something split. Maybe i should bring forth the network servers setup:
-mailman host= installed on domain.com which is our webserver (apache2 2.2.3), SLES10 SP3 with OES2 SP3. Has a separate postfix install that is not used (i seem to remember having to have this postfix instance send the email to our email server, more on this next).
-email server= separate server with Zimbra 6.0.9 FOSS (this uses postfix) running on SLES10 SP3 with OES2 SP3.The maillist users have been created. I'm not sure what else info to give you from this server.
I will happily give you remote access to the servers if you need it.