Completely read-only list
I've moved and renamed a set of lists. Not everyone reads their email, though, so occasionally people try to post to the old names off the old domain name. For now, I want to retain the old lists as is, in case I need to back out of the move.
I've set up autorespond text to tell posters that a list has moved, but their postings still go through to the old list that way. If I set everyone's moderation bit (or enable the emergency moderation flag), I still have to manually reject or discard postings.
The answer would seem to be a filter that matches on all postings and rejects them with my autorespond text. Is there anything simpler I could do?
I've checked the archives, and all the answers are about lists that are *mostly* read-only, not entirely.
A truly read-only list has other utility. There are a few extinct lists I'd like to host archives for. Mailman provides the framework for controlling who can access the archives and for generating the browsing pages.
For that use case, since I don't need an explanation sent to a would-be poster, I think the simplest solution is removing the list from the mail aliases file.
I'm using 2.1.12, for no reason other than that it's working fine and I haven't had a compelling reason to upgrade yet.
-- David.
David Lubkin wrote:
I've set up autorespond text to tell posters that a list has moved, but their postings still go through to the old list that way. If I set everyone's moderation bit (or enable the emergency moderation flag), I still have to manually reject or discard postings.
The answer would seem to be a filter that matches on all postings and rejects them with my autorespond text. Is there anything simpler I could do?
Set everyones moderation bit. Do not set emergency moderation.
Go to Privacy options... -> Sender filters and set member_moderation_action to Reject and put your message text in member_moderation_notice.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark wrote:
Set everyones moderation bit. Do not set emergency moderation.
Go to Privacy options... -> Sender filters and set member_moderation_action to Reject and put your message text in member_moderation_notice.
Why, yes, that's perfect. Thank you, Bill and Mark. Can't think why I didn't spot member_moderation_*. Now all I have to do is use withlist to change the rest of the lists.
-- David.
Mark wrote:
Set everyones moderation bit. Do not set emergency moderation.
Go to Privacy options... -> Sender filters and set member_moderation_action to Reject and put your message text in member_moderation_notice.
I replied:
Why, yes, that's perfect. Thank you, Bill and Mark. Can't think why I didn't spot member_moderation_*. Now all I have to do is use withlist to change the rest of the lists.
Actually, it's not perfect. Emergency moderation seems better than setting everyone's moderation bit.
Setting everyone's moderation bit either requires manually visiting each admin page (for ~75 lists) or writing a more complicated script to achieve what that does. Worse, it loses the record of who was set to moderation before this, making it much more cumbersome to undo.
Is there any reason you're counseling against emergency moderation?
-- David.
David Lubkin wrote:
Actually, it's not perfect. Emergency moderation seems better than setting everyone's moderation bit.
Setting everyone's moderation bit either requires manually visiting each admin page (for ~75 lists) or writing a more complicated script to achieve what that does. Worse, it loses the record of who was set to moderation before this, making it much more cumbersome to undo.
Is there any reason you're counseling against emergency moderation?
Yes. Emergency moderation is totally separate from member moderation. It is an unconditional hold without notice to the admin/moderator. It does not look at member_moderation_action or member_moderation_notice.
There is a script at <http://www.msapiro.net/scripts/set_mod.py> (mirrored at <http://fog.ccsf.cc.ca.us/~msapiro/scripts/set_mod.py>) which can be installed as bin/set_mod.py and run via
bin/withlist -a -r set_mod -- --set --all
To set all members moderated in all lists.
There is also a script at <http://www.msapiro.net/scripts/list_mod.py> (mirrored at <http://fog.ccsf.cc.ca.us/~msapiro/scripts/list_mod.py>) which you could run first to list who was moderated before hand.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro wrote:
Yes. Emergency moderation is totally separate from member moderation. It is an unconditional hold without notice to the admin/moderator. It does not look at member_moderation_action or member_moderation_notice.
Gotcha.
There is a script at <http://www.msapiro.net/scripts/set_mod.py> : There is also a script at <http://www.msapiro.net/scripts/list_mod.py> (mirrored at <http://fog.ccsf.cc.ca.us/~msapiro/scripts/list_mod.py>)
Excellent. Thanks again. Your scripts all look pretty straight-forward, but no reason to write the code when you've already written, debugged, and documented it.
-- David.
participants (2)
-
David Lubkin -
Mark Sapiro