virtual host in subscribe url
Configuring Mailman with Postfix and virtual domains. On old sever that someone else set up for me the subscribe path was:
http://mydomain.com/mailman/subscribe/announce_mydomain.com
On new site I configured it is:
http://mydomain.com/mailman/subscribe/announce
Is this merely a change across versions of Mailman or have I not configured something correctly?
Thank you,
Robin
Robin Rowe wrote:
The former URL looks like one that would come from a cPanel installation or perhaps one that uses other patches mentioned in <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.047.htp>.
Your 'new' URL is the correct one for a standard Mailman install. The only reason to consider anything else is a requirement to support lists with the same list name on different virtual hosts. Mailman as distributed doesn't do this. See the above FAQ article for more info.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark,
Thank you! Excellent answer. You're right that it was formerly cpanel.
Just wondering, isn't it a bug that by default virtual hosts Mailman namespaces collide? Why should it be considered normal to require a patch to support virtual hosts properly? In the web pages you referred me to there's some griping that cpanel was slow to share the patch. Why no rush to adopt it?
Robin
Mark Sapiro wrote:
Robin Rowe wrote:
It is not a 'bug' because Mailman was never designed to provide this support. It is a design limitation. There are plans to redo this for Mailman 3, so that Mailman 3 will provide virtual hosting support without having to worry about list name collisions across hosts.
The patches that cPanel and others have done to work around this restriction have not been accepted as appropriate for the distribution because they are generally incomplete and a kind of kludge that requires you to sometimes but not always know that your list's name is really listname_hostname rather than just listname.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Robin Rowe wrote:
The former URL looks like one that would come from a cPanel installation or perhaps one that uses other patches mentioned in <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.047.htp>.
Your 'new' URL is the correct one for a standard Mailman install. The only reason to consider anything else is a requirement to support lists with the same list name on different virtual hosts. Mailman as distributed doesn't do this. See the above FAQ article for more info.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark,
Thank you! Excellent answer. You're right that it was formerly cpanel.
Just wondering, isn't it a bug that by default virtual hosts Mailman namespaces collide? Why should it be considered normal to require a patch to support virtual hosts properly? In the web pages you referred me to there's some griping that cpanel was slow to share the patch. Why no rush to adopt it?
Robin
Mark Sapiro wrote:
Robin Rowe wrote:
It is not a 'bug' because Mailman was never designed to provide this support. It is a design limitation. There are plans to redo this for Mailman 3, so that Mailman 3 will provide virtual hosting support without having to worry about list name collisions across hosts.
The patches that cPanel and others have done to work around this restriction have not been accepted as appropriate for the distribution because they are generally incomplete and a kind of kludge that requires you to sometimes but not always know that your list's name is really listname_hostname rather than just listname.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro -
Robin Rowe