[Mailman-Developers] [Bug 1020683] Feature Request: Make regular_*_lists and *_these_nonmembers recursive (and aware of each other).

Barry Warsaw 1020683 at bugs.launchpad.net
Thu Jul 5 21:22:39 CEST 2012

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.


You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.

  Feature Request: Make regular_*_lists and *_these_nonmembers recursive
  (and aware of each other).

To manage notifications about this bug go to:

More information about the Mailman-coders mailing list