I don't think anyone anywhere has publicly talked about doing both high-volume and high-availability, at least not with Mailman.
pair.com has investigated this and put considerable resources into these questions. their newsgroups are semipublic, but i am sure if you ask Kevin Martin he can point you in the right direction. excellent people there.
kind regards philippe
--
I gather this, from all the searching I've done. I've not really found any useful information about scaling and high-availabilty/redundancy in the FAQ or anywhere else.
The HA solution will very likely be solved with a stable database/backend hook where we can store/retrieve Mailman's information -- standard scalablity on that side will be relatively straightforward.
I've not looked into the MyslqMembership hack yet. Has anyone used this?
Thanks, Forrest
------------------------------------------------------ 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
