Scott Race wrote:
>Ah, I see what's going on. So for the particular lists were working on, all
>messages to the list are held for moderation. So, it seems clicking "Accept"
>will accept the message, even if the message size is too big.
Yes, and further, if the messages are held because the poster is
moderated, this hold is applied before any of the miscellaneous holds,
so all you know is it is a post from a moderated member, and if you
approve it, it is approved even if too big.
>We recently (4 months ago) upgraded from Debian 4 to RHEL5. On the previous
>box, I believe we were running Mailman 2.1.12 (not sure), messages over the
>max_message_size limit would not hit the list and bounce back to the user with
>that message.
Without source modifications, the message would still be held, not
rejected, but the user would be notified if respond_to_post_requests
is Yes.
>The company I'm working with is hoping the system can kick back messages over
>the max_message_size before it hits moderation. Is that possible?
>
>Would adding GLOBAL_PIPELINE directives to mm_cfg.py get that done?
Yes, you could reorder the pipeline to put Hold ahead of Moderate, but
the downside of this is a non-member post could be held for one of the
miscellaneous hold reasons and the moderator may not realize it's a
non-member post.
--
Mark Sapiro <m...@msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
------------------------------------------------------
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
