[Mailman-Users] Virtual Domains: Mailman 3 timeline? Cpanel changes?

[Matt England]

At 6/12/2005 11:10 PM, Mark Sapiro wrote:
>[...] it [full Virtual Domain support] probably won't happen before Mailman 3.

I know open-source projects usually do no react well to this question, but 
I'll try anyway:

Is there a rough timeline for Mailman 3?  eg, which "order of magnitude" 
shall one use: months or years?  Another way to put it: is the Mailman 3 
design architecture outlined? done? documented?  still a twinkle in it's 
daddy's eye?

Alternatively, has anyone been asking the Cpanel people about what changes 
they made to Mailman to support full Virtual Domains (ie, email lists with 
same name on 2 diff domains via the same Mailman install binary)?  Could 
these sorts of changes possibly make it into a pre-3 release?

For what it's worth:  Mailman is the only remaining application on my web 
server system(s) that does not easily allow me to support a true 
virtual-domain server (because of the list namespace sharing/pollution 
across domains).  Namely, Apache and qmail support this stuff well (as well 
the necessary web apps sitting on Apache).  Mailman is the only one left in 
my collection of tools that I'm trying to "virtualize."

-Matt


At 6/12/2005 11:10 PM, Mark Sapiro wrote:
>Matt England wrote:
> >
> >When will Mailman natively (ie, without patches) support 2 lists with the
> >same name in different domains?
>
>It's on the ToDo list (http://www.list.org/todo.html), but unless
>someone comes up with a really good implementation in the mean time,
>it probably won't happen before Mailman 3.
>
> >I am presuming that the virtualhosts feature does not support this today;
> >if it does, can someone please reply to this thread to let me (us) know?
>
>
>You are correct. As shipped, there is only one global name space for
>list names regardless of virtual host. The virtual hosts capability
>supports things like only showing the lists for a given host on that
>host's listinfo page and allowing editing of the various templates on
>a 'per virtual host' basis, but the list names still have to be unique
>sitewide.
>
>
> >Until then, it looks like the best answer is to run separate mailman
> >installs for every independent, virtualhost domain.  Is this a fair 
> analysis?
>
>
>If it is important to allow the same list name in two domains, then
>yes, I think it is a fair analysis. The various patches for working
>around this limitation actually implement an 'invisible' list name
>which has the virtual host name appended to the list name. This should
>be a viable solution, but the number of complaints from people who've
>tried the patches leads me to think that the patches are not complete
>enough for general use.
>
>--
>Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
>San Francisco Bay Area, California    better use your sense - B. Dylan
>
>------------------------------------------------------
>Mailman-Users mailing list
>Mailman-Users at 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/mengland%40mengland.net
>
>Security Policy: 
>http://www.python.org/cgi-bin/faqw-mm.py?req=show&amp;file=faq01.027.htp