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

Mark Sapiro mark at msapiro.net
Thu Jul 5 22:29:48 CEST 2012

I wrote:
"And wouldn't this be the case if @listC was in listB's accept_these_nonmembers and @listB was in listA's accept_these_nonmembers and accept_these_nonmembers were processed recursively?"

Robert replied:
"Yes, but what if I only wanted listC to be able to send to listA and not listB (I personally don't want to do this, but I could see someone else wanting to)."

Well, if I wanted to do that, I would just put @listC in listA's
accept_these_nonmembers, but I suppose you envision a case where listB
and ListC are siblings and listB is in listA's accept_these_nonmembers
and then listC members can post to listA because some "include siblings
members as posters (recursively)" option is selected for listA, but they
can't post to listB because that "include siblings" option is not
selected for listB.

This seems so complicated and error prone that I don't think it could
even be explained in a way that people could use it, but perhaps you can
see some more straightforward way of setting this up. I also wonder if
listC members can't post to listB, how does referencing listB
(recursively) from listA give listC's members any posting rights on

In any case, I don't see it ever being implemented in Mailman 2.1 which
is virtually at the end of it's development life anyway. Perhaps
something will be done for Mailman 3.

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