- per-subscription nomail
- Web interface
- Integration with Mariachi
- List control
- Tests for bandito
- Import utilities
- Domo plugin - remote adminstration tasks
- Revisit bounce handling (VERP stuff)
- Better install
- hook into Exim
- tequila daemon
Currently this happens per users, which is too coarse.
perl Build.PL needs to grab more answers out of the existing Siesta::Config and from the user to put into the new one (generated from Config.pm.in)
password-protected archives should be easy via the mod_perl handler
one side effect of moving from Mail::Internet is that the NNTP send code will have to grow a few extra lines to invoke Net::NNTP directly.
This and the need for a nntp->siesta gateway has made me split this out into a seperate distribution.
Only allow list.owner to modify a list - only Siesta::Web enforces this.
In future it may be an idea to allow multiple owners per list
This will need a dummy Mailman config.db to test against.
Extend bandito to also steal configs from ...
* majordomo * ezmlm
Do a plugin that emulates the Majordomo command set.
One plan is this:
Nicholas Clark wants to look at this
Archive.pm should also embed optionally embed a url where the message is archived.
Maybe. This might just mean providing .debs/.rpms/ports etc etc
Like wot Mailman does
A long running tequila process