On Nov 23, 2009, at 11:28 AM, Lindsay Haisley wrote:

An ever-increasing number of software packages support the installation
of 3rd party extensions, said extensions supporting the activities of
installation, deactivation and removal, leaving the core system
unaltered. This provides end users (mail admins in the case of Mailman) with the option of installing as few or as many "extra" features as they
need or want, and offloads the task of providing everything that
everyone wants from the core developers onto a wider community of
peripheral developers who know how to work with the core package's
extension API.  Mailman has a hint of this capability already, in the
withlist utility which I've used with great success to develop a program
to expunge lists of clueless AOL users who complain to AOL that opt-in
list posts they receive from a Mailman-served list are spam.

This is a goal of Mailman 3. bin/withlist will still be there (largely unchanged), but the intent is to also support a plugin architecture to make it easy to extend Mailman in other ways, e.g. by adding handlers and other elements.

-Barry

Attachment: PGP.sig
Description: This is a digitally signed message part

------------------------------------------------------
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Reply via email to