Remove someone from list of lists but not from child lists?
All,
Just a quick question that I’m sure the answer is “not possible”. I have several lists that are subsets of users (faculty, staff, etc). Then we have a list of lists called “everyone”. But that “everyone” list gets abused by members sending out crap that people really don’t care to see.
So, I’ve had some requests to remove people from “everyone” but obviously keep them in their respective “child list”. Is this possible?
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.
btw, running mailman 2.1.14.
Thanks!
-Ryan Stasel
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
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
On 05/27/2016 11:23 AM, Ryan Stasel wrote:
Sorry, you’re right, while the lists are members, they’re all set to “nomail”.
Why are the list's members at all?
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.
It's probably fine if they are 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.
So, as long as you don't have things like @child_listname in the "everyone" list's accept_these_nonmembers, you can just remove the problem posters from that setting and their posts will then be handled according to generic_nonmember_action.
They will still receive posts to "everyone" via their regular_include_lists membership and will still be able to post to their lists of which they are members, but not to the "everyone" list.
For the children, they have nothing set in regular_*_lists.
OK
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
So, as long as you don't have things like @child_listname in the "everyone" list's accept_these_nonmembers, you can just remove the problem posters from that setting and their posts will then be handled according to generic_nonmember_action.
They will still receive posts to "everyone" via their regular_include_lists membership and will still be able to post to their lists of which they are members, but not to the "everyone" list.
Hi Mark,
Sorry, it’s not wanting to remove problem posters, sadly, that’s not currently an option. The question is can I remove people from receiving emails to the everyone list, but NOT remove them from the child lists they’re on. I’m guessing the answer is “no” without converting the “everyone” list over to just a normal list of users, as opposed to a list of lists.
Does that make sense? Basically, people want to opt-out of the everyone list.
-Ryan Stasel
On 05/27/2016 12:40 PM, Ryan Stasel wrote:
Sorry, it’s not wanting to remove problem posters, sadly, that’s not currently an option. The question is can I remove people from receiving emails to the everyone list, but NOT remove them from the child lists they’re on. I’m guessing the answer is “no” without converting the “everyone” list over to just a normal list of users, as opposed to a list of lists.
Does that make sense? Basically, people want to opt-out of the everyone list.
OK. I misunderstood.
I actually think that using regular_include_lists in the way you are is the right approach, but as you suspect, it does not allow regular members of the included lists to opt out of the "everyone" list mail.
There are two options. Those people who are digest members of all the sub-lists of which they are members (i.e. not a non-digest member of any of the sub-lists) will not receive "everyone" list mail. This is probably not a good solution for most as they probably don't want to be digest members of the sub-lists if the sub-lists are even digestable.
The other option is if they have a "decent" mail client, just set a filter so any mail which is To: or Cc: the everyone list (and maybe not To: or Cc: any of the sublists of which they are a member) is moved immediately to the trash.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On May 27, 2016, at 12:57 , Mark Sapiro <mark@msapiro.net> wrote:
On 05/27/2016 12:40 PM, Ryan Stasel wrote:
Sorry, it’s not wanting to remove problem posters, sadly, that’s not currently an option. The question is can I remove people from receiving emails to the everyone list, but NOT remove them from the child lists they’re on. I’m guessing the answer is “no” without converting the “everyone” list over to just a normal list of users, as opposed to a list of lists.
Does that make sense? Basically, people want to opt-out of the everyone list.
OK. I misunderstood.
I actually think that using regular_include_lists in the way you are is the right approach, but as you suspect, it does not allow regular members of the included lists to opt out of the "everyone" list mail.
There are two options. Those people who are digest members of all the sub-lists of which they are members (i.e. not a non-digest member of any of the sub-lists) will not receive "everyone" list mail. This is probably not a good solution for most as they probably don't want to be digest members of the sub-lists if the sub-lists are even digestable.
The other option is if they have a "decent" mail client, just set a filter so any mail which is To: or Cc: the everyone list (and maybe not To: or Cc: any of the sublists of which they are a member) is moved immediately to the trash.
Mark,
No worries. It’s a weird request… and is really a bandaid until we actually fix our mailing lists.
Thanks for the tips. I, for whatever reason, hadn’t considered a simple Exchange rule.
Thanks!
-Ryan Stasel
On 05/27/2016 12:38 PM, Mark Sapiro wrote:
On 05/27/2016 11:23 AM, Ryan Stasel wrote:
Sorry, you’re right, while the lists are members, they’re all set to “nomail”.
Why are the list's members at all?
I see that's not correctly punctuated. I meant "why are the sublists members of the everyone list?". It seems it just creates issues with things like password reminders for no reason.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Ryan Stasel writes:
So, I’ve had some requests to remove people from “everyone” but obviously keep them in their respective “child list”. Is this possible?
I think this might be possible in Mailman 3 (but would be a new feature, not implemented yet), but not in Mailman 2.
I suppose it's not socially possible to moderate (or even temporary remove posting privileges) from the folks who abuse "everyone"?
Another possibility would be to create a garbage list, and set reply-to to the garbage list on everyone. Then people who just reply-to the nearest list post will see their posts disappear into a black hole, and you can tell people who complain to "check the archives of Blackhole, if it's there, you abused 'reply-to everyone' -- don't do that". People who intentionally write to everyone ... maybe a quick whack with a 2x4 would help?
participants (3)
-
Mark Sapiro -
Ryan Stasel -
Stephen J. Turnbull