On Wed, Feb 17, 2021, at 10:24 PM, Stephen J. Turnbull wrote:
Abhilash Raj writes:
So it seems like we have some sort of agreement that we need all the roles to be able to see all the 4 states.
I think it's more like there's disagreement about which roles need to see which states, but for each role and each state, somebody thinks that role needs to see that state. I think there's agreement that it's harmless to allow everybody to see all states.
Roles here are basically Admin( i.e. list owner/moderator/site admin) and Subscriber.
In this discussion, yes. However, if we're going to take the discussion seriously, we should be more general than just this case. I think we need to consider five roles. Starting with Brian's list of List Owner, Moderator, List Member, and adding Anonymous (so that a pre-login connection has a named role) and Site Owner for completeness.
Yep, those are all the roles that even we recognize in Postorius. We also have the concept of Domain Owner, though that isn't really implemented yet.
So, from this list, List Owner and above all will use the "by_admin" state to disable if they need to and they are the only ones who can set that state.
There is no access control to transition "from" any state but each value of non-enabled states is sort of a role's way to disable the delivery. Not all states are settable by all roles.
Off-list, Ruth Ivey-Cook informs me that in "who sets what" both "who" and "what" need to be considered is what she had in mind. So I think that's exactly right and there's agreement.
Nice.
- A subscriber can only transition from any to "enabled" or "by_user" state but can see if delivery was disabled "by_admin" or "by_bounces" as separate state in the Options page.
- An admin can transition to "enabled", "by_user" and "by_moderator".
I assume you mean "by_admin" instead of "by_moderator"?
Ok, I've made a mess of it in my responses, the Core actually calls this value "by_moderator" but I have used them interchangeably in my emails. Sorry about that.
https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/interfaces/memb...
They should use "by_user" when acting on behalf of the user and other when there are any administrative reason to disable delivery, whatever that may be. I expect "by_admin" to be used sparingly, and I don't see any use cases for it.
- Mailman itself will use the "by_bounces" to disable delivery due to bounces.
Is that an accurate description?
+1 for 1 -- 3 as written. Others' mileage may vary.
Cool, thanks!
Steve
-- thanks, Abhilash Raj (maxking)