Hi,
just to chime in: the bigger issue I see with our (non english native)
list owners is the confusion between "Accept immediately (bypass other
rules)" and "Default processing", in particular during moderation of a
held message to set the status of a new list member which was hold for
moderation as list default.
People tend to choose "Accept immediately (bypass other rules)".
"Default processing" doesn't include "Accept" which I think is the
reason. They want to accept the member. They want to accept it now, i.e.
"immediately". They choose Accept.
I keep regularly telling them that they don't want "Accept immediately
(bypass other rules)" ever. But it's not intuitive for list owners with
litte moderation volume.
I check the database occasionally for members set to immediate and
change it to default processing. I'll keep reminding people. But it
still happens.
I think something like "Default Accept" or "Standard Accept" would be
better.
And also changing the "Accept immediately" to something which makes it
more clear that it's "dangerous" would be helpful to keep people from
choosing it.
But I haven't found the best names for them either, yet.
I do wonder somehow if there is really a use case where you would
actually need "Accept immediately". For our lists I haven't seen it,
yet, but to be honest, it's not totally clear to me what the default
processing rules do exactly...
Cheers,
Gerald
On 13.08.25 14:59, Sam Darwin via Mailman-users wrote:
I don't understand why you are confused.
I understand now, and I'm not confused. However before, when I was learning
about this topic, I encountered a problem, and it's worth trying to make it
easier. Even now that I 'understand', the issue continues.
It's about terminology and language, and not about the functioning of mm3.
There are distinct choices. You'd like to easily remember them, in your mind,
and be able to quickly explain to yourself, or to someone else.
- "list default". I would just think "Ok, clearly that's the default. Look at the
name there. List default. The default."
- "default processing'. I would just think "Ok, clearly that's the default. Look at
the name there. Default processing. The default."
Yes, we know they're different. What is the mnemonic device to remember each
one. Couldn't they be named differently?
99% of the time, you can remember "a config file", "the executable", "the bin
directory", you can remember a thing based on what it's called, and those don't conflict with each other.
But if you name both of your sons "Michael" even though you understand they are
separate people, it causes headaches.
If you choose a naming scheme such as "the red automobile" versus "the red car", and then
ask the person "don't you understand, those are two different things for us. Why are you confused? They
are two separate things. You know that. Why are you confused." Answer: the problem is the choice of
naming.
So ask the question is "default processing" the only compelling name for that functionality? The word "default" is already used
for "list default". Why use it again? Why not "Standard Processing -- run additional checks and accept the message." Or
"Regular Processing". "Typical Processing". Anything besides "default". Invent a new word: quark-spark processing.
(well, don't use 'fallback' because it's just a synonym.)
well, just trying to answer "why you are confused". maybe I am being too
repetitive already.
_______________________________________________
Mailman-users mailing list -- mailman-users@mailman3.org
To unsubscribe send an email to mailman-users-le...@mailman3.org
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Archived at:
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/NIHQRALYG5FY3J3IJ43WTQCGFWSULXQC/
This message sent to v...@spamcop.net
_______________________________________________
Mailman-users mailing list -- mailman-users@mailman3.org
To unsubscribe send an email to mailman-users-le...@mailman3.org
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Archived at:
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/SFTBXZ4AVHCXWLLVN5JIB6ZK5FIL52EB/
This message sent to arch...@mail-archive.com
