Next steps for ezmlm-idx

Greetings.

I have a lot of ideas for some big things things that should be changed
in or added to ezmlm-idx, but I would like to hear from you what you
would most like changed.

Here are some of my ideas:

1. A custom ezmlm outgoing queueing and delivery system, equivalent to
qmail-queue+qmail-remote, that is able to do custom substitutions on the
messages as they are being delivered.  The most obvious substitution
would be the subscriber address, but in time the subscriber's name could
also be substituted.

2. Alternate storage mechanisms for the archive, such as being able to
store the archive in SQL much like the subscriber list, or in a DBM file
etc.

3. Standardized web interface.  This would be a CGI script or set of
scripts, probably written in Python, with two parts: an administrative
part for setting up and managing lists, and a subscriber part for web
based subscription management and the like.

Do you have other ideas?

Thanks.

-- 
Bruce Guenter <[email protected]>                http://untroubled.org/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iD8DBQFIyX+R6W+y3GmZgOgRApOfAKCh9NGsKwmxbRDf6y/0uvUn0Cu8QgCfRxBz
SOOR/lYS+aIH7g7IW1XUKA4=
=pR9X
-----END PGP SIGNATURE-----