[Mailman-Users] Mailman 2.1.10 has been released

[Mark Sapiro]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mark Sapiro wrote:
|
| I think the best solution is to turn off the preservation of
| unparseable messages, and add an mm_cfg.py setting to turn it on. I
| can work up a patch.
|


A patch is attached. It doesn't turn off preservation by default because
it piggybacks on an existing Defaults.py/mm_cfg.py setting which was
lately used only by bin/update. The Defaults.py setting is

QRUNNER_SAVE_BAD_MESSAGES = Yes

Setting

QRUNNER_SAVE_BAD_MESSAGES = No

in mm_cfg.py will stop preserving the unparseable messages, but certain
other problem qfiles will still be preserved. Additionally, preserved
files will be stored in qfiles/bad and not qfiles/shunt. Finally, if
QRUNNER_SAVE_BAD_MESSAGES = No, the log message will revert to the old
"Ignoring unparseable message:".

Brad,

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

and set

QRUNNER_SAVE_BAD_MESSAGES = No

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.

- --
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)

iD8DBQFIDVAhVVuXXpU7hpMRAqHBAKCFODqF84UhBYnRvblS00eX4roxdQCeNOXl
amZX+XRwrdd9RpIE80eOFKM=
=vi+P
-----END PGP SIGNATURE-----
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 2.1.10.patch.txt
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20080421/dceffdf2/attachment.txt>