hi there,
I run check_perms with the -f switch and the program runs the program
claims it found 100 problems and asks to run the program again. Next
time I run it 100 problems are still found. So I did some research to
figure out what the problems are.
$ sudo ./check_perms -f
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
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
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
Noah wrote:
I run check_perms with the -f switch and the program runs the program
claims it found 100 problems and asks to run the program again. Next
time I run it 100 problems are still found. So I did some research to
figure out what the problems are.
$ sudo ./check_perms -f
Hello,
I am curious what would cause an outgoing queue runner process to increase in
memory usage, when Mailman is idle?
I am running 4 outgoing qrunner slices, using this in mm_cfg.py:
try:
QRUNNERS.remove(('OutgoingRunner', 1))
QRUNNERS.append(('OutgoingRunner', 4))
except ValueError:
