On Jun 13, 2011, at 07:22 PM, Richard Wackerbarth wrote: >This seems "out of place" for MM, per se. Providing this material is >something that is intimately tied to the archiver. > >As I see it, the only thing that MM can do is to provide a "pass thru" >conduit to whatever archiver the installation has chosen.
I think this is exactly right for read-only NNTP, and in fact the current MM3 NNTP bridge could probably be rewritten as an archiver plugin (that's not a bad idea for someone looking to do a bite-size branch!). I think there would need to be tighter integration for the posting side, a la Gmane. Unlike Gmane though, if you post through NNTP and we "know who you are", we wouldn't need to do the verification dance. -Barry
signature.asc
Description: PGP signature
_______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org http://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: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
