On Jul 05, 2012, at 01:58 PM, Richard Wackerbarth wrote: >First, I presume that you are willing to restrict yourself to the case where >lists listA, listB, and listC are served by the same instance of MM. On the >distribution side, that restriction certainly is not necessary for list >inclusion, but, in general, there is no mechanism for listA to learn the >members of listC unless they are served by a common server instance. > >Even so, the issue is whether, or not, everyone who receives listB should be >allowed to submit to listA (without moderation). Or perhaps you would only >want those who can make unmoderated submissions to listB to have that >transitive permission.
I'll note that with Mailman 3 and clever implementation of the IRoster interface, various riffs on this should be doable. Most implementations of IRoster are not physical objects persisted in the database, but instead "virtual" objects such as queries. There's no reason I can think of that an IRoster implementation couldn't perform cross-list queries, or even for that matter cross-server queries, assuming the necessary communication channels were available. I've not actually tried to implement anything like this, but I can somewhat visualize how this would work. I invite you to experiment with this. Cheers, -Barry _______________________________________________ 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
