>>>>> "RB" == Richard Barrett <[EMAIL PROTECTED]> writes:
RB> The qrunner puts badly formatted messages that it cannot cope
RB> with into shunt. It also error logs information about the
RB> exception that caused it to make that decision.
To be really anal about it :) messages that enter the system
unparseable will be put in qfiles/bad if QRUNNER_SAVE_BAD_MESSAGES is
set to 1 in mm_cfg.py. By default this variable is set to 0, which
discards unparseable messages. On python.org, we get maybe two such
messages a month, and they've always been /really/ poorly formatted
spam (just "poorly formatted", and the parse should be able to
adjust).
The only messages in qfiles/shunt should be ones that triggered bugs
in Mailman. There should always be an entry in logs/error
corresponding to the shunted message.
RB> There is also a script $prefix/bin/unshunt that takes things
RB> from the shunt and tries to process them again.
RB> But you presumably need to fix the problem in the message with
RB> your trusty text editor or it'll just get shunted again.
Usually, you (or really, I :) need to fix the Mailman bug that caused
the shunt before unshunting will do anything useful.
-Barry
------------------------------------------------------
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [email protected]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
