On 4/21/08, Mark Sapiro wrote:
If you could apply this patch (you can apply it directly to the
installation directory, by e.g.
cd /usr/local/mailman
patch -p0 < path/to/2.1.10.patch.txt
Patch applied fine, no complaints.
and set
QRUNNER_SAVE_BAD_MESSAGES = No
Done.
in mm_cfg.py and restart Mailman, things should be back more or less the
way they were in 2.1.9.
I have applied the patch to my installation and I'm sure it's good, but
I haven't seen any unparseable messages.
I haven't seen any more unparseable messages in the last few minutes,
but let's see how things go.
--
Brad Knowles <[EMAIL PROTECTED]>
LinkedIn Profile: <http://tinyurl.com/y8kpxu>
_______________________________________________
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives:
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
