Dear List,
I find the use of the term 'None' (or 'Kein' in the German translation; see attachments) in the 'Moderation action' column of the member list misleading, as the term suggests that no moderation action is applied to the respective member.
However, this is not necessarily the case. If you check a member’s "Administration options / Moderation" setting, a moderation action, such as "Moderation" or "List default", may be in effect.
I suggest that the 'Moderation action' column should display the currently set value of the 'Administration options / Moderation' setting for each member. Since some of our mailing lists frequently add and remove thousands of members, manually adjusting this setting for each member would not be practical.
Best regards, Markus Grandpré
-- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342
Mailman's content filtering has removed the following MIME parts from this message.
Content-Type: image/png Name: mm3_memberlist_de.png
Content-Type: image/png Name: mm3_memberlist_en.png
Markus Grandpré writes:
I find the use of the term 'None' (or 'Kein' in the German translation; see attachments)
This list does not allow attachments. Please be more explicit in your explanations (see comments below), or (preferred, because it's unlikely that action will take place soon, and mailing list conversations are forgotten in a few weeks at most) create an issue (probably at https://gitlab.com/mailman/postorius/-/issues/) and attach the files there.
in the 'Moderation action' column of the member list misleading, as the term suggests that no moderation action is applied to the respective member.
However, this is not necessarily the case. If you check a member’s "Administration options / Moderation" setting, a moderation action, such as "Moderation" or "List default", may be in effect.
I don't understand. My users are pretty innocuous so "List default" and "Default processing" are in fact what is displayed in my installation (Mailman 3.3.10 and Postorius 1.3.13). If I change one subscriber to "Hold", that is what is displayed after refreshing the user list screen.
What versions of Mailman and Postorius are you using?
If you are using current Mailman, perhap the German translation is inaccurate.
I suggest that the 'Moderation action' column should display the currently set value of the 'Administration options / Moderation' setting for each member.
See also https://gitlab.com/mailman/postorius/-/issues/188 for a related issue in a different context (the user's preferences page). The issue there is wanting the effective setting in cases where a list or user setting is in effect but the user's list of subscriptions shows "----".
On 2/4/25 02:51, Markus Grandpré wrote:
Dear List,
I find the use of the term 'None' (or 'Kein' in the German translation; see attachments) in the 'Moderation action' column of the member list misleading, as the term suggests that no moderation action is applied to the respective member.
However, this is not necessarily the case. If you check a member’s "Administration options / Moderation" setting, a moderation action, such as "Moderation" or "List default", may be in effect.
This is https://gitlab.com/mailman/postorius/-/issues/577 fixed in Postorius 1.3.9 by https://gitlab.com/mailman/postorius/-/merge_requests/811
See the UI changes at https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-9
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Dear Mr Sapiro, dear Mr Turnbull,
thank you very much for your reply. For clarification I like to change:
What versions of Mailman and Postorius are you using?
- mailman3, v3.3.8-2~deb12u2
- mailman3-web, v0+20200530-2.1
- python3-django-mailman3, v1.3.9-1
- python3-django-postorius, v1.3.8-3
- python3-mailman-hyperkitty, v1.2.1-1
- python3-mailmanclient, v3.3.5-1
with Debian GNU/Linux 12 (bookworm). So the newest changes:
This is https://gitlab.com/mailman/postorius/-/issues/577 fixed in Postorius 1.3.9 by https://gitlab.com/mailman/postorius/-/ merge_requests/811
are not yet available on our system. Hopefully we won't have to wait too long with Debian as there is already a lot of confusion among some of our many list administrators as we only started using Mailman3 for production a few days ago.
Best Markus
Am 04.02.25 um 19:25 schrieb Mark Sapiro:
On 2/4/25 02:51, Markus Grandpré wrote:
Dear List,
I find the use of the term 'None' (or 'Kein' in the German translation; see attachments) in the 'Moderation action' column of the member list misleading, as the term suggests that no moderation action is applied to the respective member.
However, this is not necessarily the case. If you check a member’s "Administration options / Moderation" setting, a moderation action, such as "Moderation" or "List default", may be in effect.
This is https://gitlab.com/mailman/postorius/-/issues/577 fixed in Postorius 1.3.9 by https://gitlab.com/mailman/postorius/-/ merge_requests/811
See the UI changes at https://docs.mailman3.org/projects/postorius/en/ latest/news.html#news-1-3-9
-- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342
Markus Grandpré writes:
Hopefully we won't have to wait too long with Debian
Debian has traditionally been quite slow to update Mailman, and they're following tradition. Both the testing and unstable distributions are still on Mailman 3.3.8. Regarding your specific issue of Kein/None, testing has the same version of mailman-web (dated 2020-05-30), while unstable has a much newer version of mailman-web (dated 2024-03-12). That should resolve that issue, but you will have to wait a full Debian development cycle at least.
Our standard recommendation is to do a source installation in a Python virtual environment, point the new installation at your $SQLDB, review the content of /etc/mailman3 (I think Debian puts mailman3 configs there and that's what we recommend), test the new installation, and if that works, remove the Debian installation after preserving the /etc/logrotate.d/mailman*, /etc/cron.d/mailman*, and /usr/lib/systemd/system/mailman*.service files which are probably generally appropriate for Mailman 3 installed in a Debian system.
There is also a containerized distribution of Mailman 3 suite, but I don't know how straightforward it is to port over a Debian packaged system to that environment.
It may sound pretty fearsome, but you can hire people to do the installation and testing (maybe for as little as a pizza and a mug of beer ;-). After that you will get a more reliable system and better support (really, almost all the Reply Guys here run up-to-date systems of that kind, so we're much more familiar with it than with distro installations).
Steve
participants (3)
-
Mark Sapiro -
Markus Grandpré -
Stephen J. Turnbull