Imagine an installation with 500+ mailing lists and almost as many local admins that are supposed to maintain their own local lists with a few local members. As site admin, I see all 500+ lists, but I was expecting *local* admins to see only the lists they maintain. I have set all lists to "advertised = False", so they are hidden from ordinary view. Is there a way to show only relevant lists to local admins?
I am running docker running release. mailman info GNU Mailman 3.2.0a1 (La Villa Strangiato)
Thor Atle Rustad
On 01/23/2018 12:10 PM, Thor Atle Rustad wrote:
Imagine an installation with 500+ mailing lists and almost as many local admins that are supposed to maintain their own local lists with a few local members. As site admin, I see all 500+ lists, but I was expecting *local* admins to see only the lists they maintain. I have set all lists to "advertised = False", so they are hidden from ordinary view. Is there a way to show only relevant lists to local admins? Are we talking about Postorius or Hyperkitty? There is no way for users that do not have the django superuser permission, to see unadvertised lists in the Postorius list index. I just doublechecked the source. There is an issue about list filtering/search for the index page.
2018-01-23 14:37 GMT+01:00 Simon Hanna simon@hannaweb.eu:
On 01/23/2018 12:10 PM, Thor Atle Rustad wrote:
Imagine an installation with 500+ mailing lists and almost as many local admins that are supposed to maintain their own local lists with a few local members. As site admin, I see all 500+ lists, but I was expecting *local* admins to see only the lists they maintain. I have set all lists to "advertised = False", so they are hidden from ordinary view. Is there a way to show only relevant lists to local admins?
Are we talking about Postorius or Hyperkitty? There is no way for users that do not have the django superuser permission, to see unadvertised lists in the Postorius list index. I just doublechecked the source. There is an issue about list filtering/search for the index page.
I believe I wrote Postorius in the subject line, but it may not be so obvious. So yes, in Posterius I would like to hide the lists from email harvesters, while relatively "untrusted" admins should have access to basic operations on the one list he/she "owns" (and without having to browse through 50 pages of mailing lists). Somehow I don't think 500 superusers in our system is a good idea!
On January 23, 2018 6:26:51 AM PST, Thor Atle Rustad thor.rustad@gmail.com wrote:
2018-01-23 14:37 GMT+01:00 Simon Hanna simon@hannaweb.eu:
On 01/23/2018 12:10 PM, Thor Atle Rustad wrote:
Imagine an installation with 500+ mailing lists and almost as many local admins that are supposed to maintain their own local lists with a few local members. As site admin, I see all 500+ lists, but I was expecting *local* admins to see only the lists they maintain. I have set all lists to "advertised = False", so they are hidden from ordinary view. Is there a way to show only relevant lists to local admins? I believe I wrote Postorius in the subject line, but it may not be so obvious. So yes, in Posterius I would like to hide the lists from email harvesters, while relatively "untrusted" admins should have access to basic operations on the one list he/she "owns" (and without having to browse through 50 pages of mailing lists). Somehow I don't think 500 superusers in our system is a good idea!
What do you mean by local admins?
Is this
Giantsite.example.com hosts lists for a bunch of domains, and you want the logged in admins of mydomain.com to see their list admin pages but not otherdomain.org's lists
You want each logged in admin to have their own personal dashboard of list admin pages for lists they administrate, even though they're all under one big domain.
(Neither of those scenarios talks about archives, since you say you're only talking about postorious)
I think #2 is something we should be doing, and the old "todo" section of the interface kind of was made with that in mind. Probably worth mocking up some screenshots and opening a feature request to keep the idea in mind, but it should be more a matter of prioritizing how things are displayed than any huge change.
I'm not sure if we have a "local admin" concept in the system that lines up with #1, though.
2018-01-23 16:59 GMT+01:00 Terri Oda terri@toybox.ca:
On January 23, 2018 6:26:51 AM PST, Thor Atle Rustad < thor.rustad@gmail.com> wrote:
2018-01-23 14:37 GMT+01:00 Simon Hanna simon@hannaweb.eu:
On 01/23/2018 12:10 PM, Thor Atle Rustad wrote:
Imagine an installation with 500+ mailing lists and almost as many local admins that are supposed to maintain their own local lists with a few local members. As site admin, I see all 500+ lists, but I was expecting *local* admins to see only the lists they maintain. I have set all lists to "advertised = False", so they are hidden from ordinary view. Is there a way to show only relevant lists to local admins? I believe I wrote Postorius in the subject line, but it may not be so obvious. So yes, in Posterius I would like to hide the lists from email harvesters, while relatively "untrusted" admins should have access to basic operations on the one list he/she "owns" (and without having to browse through 50 pages of mailing lists). Somehow I don't think 500 superusers in our system is a good idea!
What do you mean by local admins?
Is this the logged in admins of mydomain.com to see their list admin pages but
- Giantsite.example.com hosts lists for a bunch of domains, and you want
not otherdomain.org's lists
- You want each logged in admin to have their own personal dashboard of list admin pages for lists they administrate, even though they're all under one big domain.
(Neither of those scenarios talks about archives, since you say you're only talking about postorious)
I think #2 is something we should be doing, and the old "todo" section of the interface kind of was made with that in mind. Probably worth mocking up some screenshots and opening a feature request to keep the idea in mind, but it should be more a matter of prioritizing how things are displayed than any huge change.
I'm not sure if we have a "local admin" concept in the system that lines up with #1, though.
Ok, this would more like number 2. It's National.dogclub.com with its various mailing lists like poodle.dogclub.com, which expands to poodle-regionA.dogclub.com, poodle-regionB.dogclub.com, poodle-regiionC.dogclub.com and so on. So with dozens of different dog breeds and geographic chapters, the number of mailing lists are between 500 and 1000, but all are under the same dogclub.com domain. The members of each list should be maintained by a person with some elevated rights, but not enough to mess up the system. What I called "local admin" should have rights to add and remove members of, say, the poodle-regionA mailing list.
On 01/23/2018 08:54 AM, Thor Atle Rustad wrote:
What I called "local admin" should have rights to add and remove members of, say, the poodle-regionA mailing list.
By "local admin", do you mean "list owner", i.e., a list owner should be able to see her own "hidden" lists.
Is that what you mean, or to you envision some new category of user that has more access than a list owner?
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
2018-01-23 18:40 GMT+01:00 Mark Sapiro mark@msapiro.net:
On 01/23/2018 08:54 AM, Thor Atle Rustad wrote:
What I called "local admin" should have rights to add and remove members of, say, the poodle-regionA mailing list.
By "local admin", do you mean "list owner", i.e., a list owner should be able to see her own "hidden" lists.
Is that what you mean, or to you envision some new category of user that has more access than a list owner?
-- 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@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
I mean "list owner"
participants (4)
-
Mark Sapiro -
Simon Hanna -
Terri Oda -
Thor Atle Rustad