Brie Yoder via Mailman-Users writes: > [Running Mailman 2.1.39 on Dreamhost]
I don't know much about Dreamhost. Is this managed by cPanel or a similar system, or do you have direct access to Mailman? > I am attempting to create a 2-tiered list of subscribers to a > Mailman list, where everyone would receive all posts (modulo those > whose subscription is paused, etc.), and a 2nd tier (subset of > everyone) who would be allowed to post. This would be different > than setting the ‘mod’ bit for each user - it would be something > only a list admin/moderator could change, That is true for setting the mod bit. If it weren't, the mod bit wouldn't be useful. I do not believe that *moderators* can access the mod bit; that should require the *list owner* password. In my experience many lists simply giving all the moderators the owner password (and saying no more -- frequently those folks never realize they could, say, delete the list or lock out the "real" owner). I've never heard of that causing trouble (although obviously it *could*, that's your call, I'm just saying a lot of owners find the tradeoffs useful). > and would allow an immediate rejection of posts, with an optional > rejection message for non-2nd tier subscribers. This may be possible in Mailman 2.1, but I don't have an instance to check. I think there were list-wide hold and rejection messages, and moderation actions, and then setting the mod bit would do pretty much what you want. It is definitely possible in Mailman 3 on a subscription-by- subscription basis, including the optional rejection message. However, moderators still do not have access to the moderation setting except when handling a moderated post from an address, and the tradeoffs for granting owner privilege are somewhat different. To make it convenient and consistent for a whole list, you would have to write a script to do it, either a "withlist" script for use with Mailman 3's "mailman" administration utility, or a script that would access the REST API (this would require additional setup on the Mailman host for authentication if you wanted to allow remote connections from the script). We can help with the scripts themselves but I strongly recommend you work with local admins for how to do authentication and whether to allow remote access at all. Mailman itself effectively only has a "Mailman superuser" account -- once you have access to the REST API you can pretty much do anything. You could try using the front-end httpd's access-to-location controls, but I don't think that's safe. Because both Mailman 2.1 and Python 2 are end-of-life and neither is receiving even security patches at this point, we *strongly* recommend upgrading to Mailman 3. For further information on Mailman 3, I *strongly* recommend posting to "Mailman 3 Users" <mailman-us...@mailman3.org>. There are many savvy and experienced users there, someone may have done what you want to do and even a script for configuring a whole list at once. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan ------------------------------------------------------ Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/ Member address: arch...@jab.org
