Barry wrote: > I think I've stated my general philosophy in a previous message. > If WizzyMTA came with a new plug-in, documentation, and some promise > of support help (if only to answer questions on mailman-users), we'd > probably add the module in the next release. If we had a similar plug-in > architecture for multiple 3rd-party archivers, we'd facilitate the same > kind of thing for that service. I'd be all for that.
Thanks for your feedback. I'll be happy to dig into the current archive system and work on a plug-in architecture to support multiple external archivers. I originally thought the Archive component of Mailman was something intended only to support the local pipermail archive, but using that API like you mention sounds like it would work well. I'm guessing it'd be a fair amount of work to make the internal pipermail work with the plug-in approach just like the external archivers. At the very least, it would need a lot of testing to make sure it doesn't break existing installations. I'll get back with MARC and possibly GMane so I can try to make things as general as is reasonable. I'll try to run a proposed approach in front of the list before coding it (unless it's easy enough to demonstrate the proposal via code). I think the only concern is that I think admins *would* find value in per-list control of external archives. This is speculation, though. Jeff _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org 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
