Re: [Mailman-Users] mm2.1 - message is unparsable

2003-01-03 Thread Bryan Fullerton
On Thursday, January 2, 2003, at 11:24 PM, Barry A. Warsaw wrote: This is normal, and no, you don't need to worry about the lost data files. In fact, once you get comfortable that the only bad messages are spam, you can set QRUNNER_SAVE_BAD_MESSAGES=0 in your mm_cfg.py to just discard them. I

Re: [Mailman-Users] mm2.1 - message is unparsable

2003-01-02 Thread Barry A. Warsaw
> "BF" == Bryan Fullerton <[EMAIL PROTECTED]> writes: BF> I guess now that mm2.1 has been released, general questions BF> should go here? If not, let me know and I'll send to -dev. Yes. For now, I'm reading this list and trying to answer questions just to get folks familiar with 2.1

[Mailman-Users] mm2.1 - message is unparsable

2003-01-02 Thread Bryan Fullerton
I guess now that mm2.1 has been released, general questions should go here? If not, let me know and I'll send to -dev. Just installed mm2.1 and moved over some lists yesterday. Today I found the following in logs/error: Jan 02 18:58:19 2003 (35619) message is unparsable: 1041551899.569575+7753