Hi Mark,
Sorry, you’re right, while the lists are members, they’re all set to “nomail”.
The list does have a couple individuals, but not many. They’re really only there so they can send. But obviously I could put them in non-members.
Nothing is in regular_exclude_lists. regular_include_lists is as I said, more lists. A lot of individual emails is n accept_these_nonmembers. Basically everyone that can send to the list.
For the children, they have nothing set in regular_*_lists. So really, the “tree” is only 2 high. staff, faculty, gtfs, admins, etc, then the everyone list that contains those.
Thanks!
-Ryan Stasel
On May 27, 2016, at 11:17 , Mark Sapiro <mark@msapiro.net> wrote:
On 05/27/2016 10:38 AM, Ryan Stasel wrote:
So, I’ve had some requests to remove people from “everyone” but obviously keep them in their respective “child list”. Is this possible?
I need more specifics to answer.
The everyone list is set up with the child lists being members, then also setting regular_include_lists so that people that are part of multiple child lists don’t get duplicates.
If a child list is a member and also in regular_include_lists, I think this would create rather than avoid duplicates.
Anyway, to say more, I need more details of the list configurations such as for the "everyone" list, are there individuals and lists as members or just lists, what's in accept_these_nonmembers, what's in regular_*_lists, and for the children, what's in regular_*_lists?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/rstasel%40uoregon.edu