Re: Next steps for ezmlm-idx

Peole,


Lars Kruse wrote:
> Hi,
> 
>> 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.
> 
> I would really like it, if this could be pluggable. I am currently working on
> an encryption add-on for ezmlm mailing lists, but for now this requires a
> wrapper around qmail-queue. If your work could make this part easier, then I
> would be very happy!
> 
> 
>> 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.
> 
> yes - a subscription web-interface would indeed be great.
> I am currently maintaining the ezmlm-web interface
> (https://systemausfall.org/toolforge/ezmlm-web/), which is written in perl. If
> you think, that this could be common base for a future interface, then I would
> be happy, of course.
> But since I grew a little bit tired of perl ("ezmlm-web" was originally
> developed by Guy Antony Halse - I took over the project in 2005), I would also
> be happy to contribute to a new python replacement.


I would prefer Ruby.

Thanks,

Phil.
-- 
Philip Rhoades

GPO Box 3411
Sydney NSW	2001
Australia
E-mail:  [email protected]