what I did with my system was make the archiver completely separate from Mailman -- to mailman , it's just another email address that the admin subscribes, or not. Does archiving need to be integrated into mailman in the first place? As opposed to, say, a place to specifiy the URL of the archives for display?
and since we've never really had the time/energy/etc to maintain and enhance pipermail, maybe spliting the code out and retiring it is a good strategy. On May 12, 2005, at 4:15 PM, Barry Warsaw wrote: > Let's say that's an important requirement. What I'd like to see in > that > case is a way to specify multiple archivers, register these archivers > with Mailman, and then give list owners the ability to select one or > more of those registered archive methods. You could even > generalize it > so that the internal Pipermail archiver was just another one of those > methods. _______________________________________________ Mailman-Developers mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-developers 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-developers/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
