Andrew Stuart writes: > Can anyone point me in the direction of a good explanation of how > archiving works?
There isn't one. Mailman core doesn't define an archiving function and current opinion is that it shouldn't. It just defines an interface for attaching the archiver or archivers you prefer to the system. The main reason there actually *is* a defined interface is so that core can provide the permalink for use in a header field. Otherwise integrating an archiver is trivial (on the Mailman core side) and archiver-specific. > Is there any reason why it should not be possible to be able to > pull messages scheduled for archiving out through the REST API as > file attachments? Sure. There's no reason to suppose that the messages are available to the REST API. One popular scheme involves subscribing a list-specific address at mail-archive.com, which is a third-party service. The messages come in, the messages go out, and they leave no trace of content behind, just log entries. _______________________________________________ Mailman-Developers mailing list [email protected] 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
