Ace Suares wrote:
>
>But unfortunately we already have
>add_virtualhost('list.domain.com', 'list.domain.com') in place, since the
>webinterface is at https://list.domain.com and the mail gets handled
>@list.domain.com
Mailman is just doing what seems to me to be the right thing. You have
add_virtualhost('list.domain.com', 'list.domain.com')
because you want list mail sent to the list.domain.com domain. The
'mailman' address is just another list, so it's address is
[EMAIL PROTECTED]
Granted, if you have multiple domains, this gets tricky. There is only
one 'mailman' list and it is the same list for all domains, yet its
address gets displayed on the listinfo overview with the email domain
corresponding to the current URL domain. The reason for this is that
in a virtual hosting environment, you may not want to expose a
different domain name on the listinfo overview page.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
------------------------------------------------------
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
