As I understand it, currently there are a few default archivers including prototype, mhonarc and mailarchive. New archivers can be plugged in by implementing an archiver which complies to the archiver interface. Not hard but still requires coding skills.
Specifically if would be good if a Mailman admin could define in the Mailman config file a set of destination email addresses and POST urls that archive messages are sent to. This would meet many common archiving needs via configuration instead of code. It’s a little odd that Mailman basically does this at the moment but only for mail-archive.com I’m proposing this be a bit more generalised and also that a generalised POST archiver be included. I’d also include a filesystem/zip archiver which writes each message to a zipped file on the disk. I’d be happy to implement assuming anyone else sees value in it, ideally with some architectural input from core developers. Thoughts anyone? as _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
