At 1/26/2006 09:43 PM, Mark Sapiro wrote: >There are some patches around. See ><http://sourceforge.net/tracker/index.php?func=detail&aid=943827&group_id=103&atid=300103>. >There is also a link to cPanel's patches at ><http://mail.python.org/pipermail/mailman-users/2005-January/041748.html>. >But reports from people who've tried these suggest that they may be an >incomplete solution at best, and may not work at all.
Ok, thanks. So the question is: is there any move afoot to change Mailman to support same list names across multiple domains? Why can't Mailman index it's list names such that the domain name is associated with the internal list name...thus allowing for the internal structure to have the same list name for different domains? I suspect the answer: it's hard because that support was not build into the architecture. And that's a fine answer for me. The followup question (assuming the above answer...which may or may not be a fair assumption): will this architecture ever be changed to remove this limitation? -Matt ------------------------------------------------------ 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
