I've:

       http://github.com/justingit/dada-mail/tree/c9129c66b8dd48ed9e48784ce4a0f7f87a476e1a

finally pushed a version of Dada Mail up into github that includes the features that covers basically the entire feature spec, as outlined:

       http://dadamailproject.com/fundraiser.html#multiple_fields__subscribereditable_fields
To jog your memory:



Currently, Dada Mail supports adding/editing/deleting of arbitrary subscriber fields.

It also supports the list owner logging into the list control panel and editing the subscriber information, on a per-subscriber basis.

Dada Mail currently does not support the actual subscriber to edit it's own subscriber information and we'd like to add that feature into Dada Mail.

This would also mean we'd have to overhaul the session management part of Dada Mail to not only support admin sessions for the list owner, but to also support sessions for individual users.

Once completed, individual subscribers will be able to edit their own subscription information, add/edit/remove themselves from mailing lists their subscribed from and view other meta information about their current subscriptions.

We'd also like to have more advanced web-based features available for subscribers, once logged into Dada Mail, including the option to posting and replying to discussion list messages from within your web browser, having the archive accessible to subscribers only.

[/quote]

I've attached a screenshot to this message of what the, "profile home" currently looks like for a subscriber. All the functionality if fleshed out and works. It needs a little design work and bugs will surely come to the surface, but it's almost ready to be used. This new feature will also replace the currently broken, "update_subscription.cgi" extension, which had no real authentication (a very big problem)

So, that's fun. I don't really know what else to do with the program at this point. I'll release a new alpha/beta release of the program, but currently, the feedback I've gotten on these releases is very few and far between, as people DON'T test out the development versions and only give me, "It doesn't work" reports after a, "Stable" release. Is there anything I can do, for the community, to make it easier for people to test out the program?

Any questions about this (BIG) new feature?

--
Justin J.