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

Richard Wackerbarth richard at nfsnet.org
Thu Jul 5 22:33:29 CEST 2012


On Jul 5, 2012, at 2:48 PM, Robert Arlt Jr. wrote:
> I can as well.  In my view of the issue I believe that allowing everyone
> on listB to submit is the better option as I can easily make a list
> composed of those allowed to send unmoderated to listB, call it listB2
> and add listB2 to listB then use listB2 as the list allowed to send to
> listA (all of this assuming recursion is implemented).

But that would be confusing to the members of listB. They would have to
realize that they are not really a member of listB, but that they are
actually a member of listB2.

So, if you are going to do that, and perhaps for any inclusion that is
transparent on message delivery, an attempt to change delivery
preferences on listA should take the user to the listB2 preferences.

However, if the delivery of listA is done by publishing a copy of the
message on listB, then, for the purpose of preferences, the listB user
should not be considered a member of listA.

-- 
You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.
https://bugs.launchpad.net/bugs/1020683

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/mailman/+bug/1020683/+subscriptions


More information about the Mailman-coders mailing list