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

[Barry A. Warsaw]

>>>>> "BF" == Bryan Fullerton <bryanf at samurai.com> 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.  At some point I'm going to fall
behind <wink> and start relying on you guys to help point me to
threads I need to read.

    BF> Just installed mm2.1 and moved over some lists
    BF> yesterday. Today I found the following in logs/error:

    | Jan 02 18:58:19 2003 (35619) message is unparsable: 
    | 1041551899.569575+77534d9e5771753ab3fb0698e063c621da3b4223
    | Jan 02 18:58:19 2003 (35619) lost data files for filebase: 
    | 1041551899.569575+77534d9e5771753ab3fb0698e063c621da3b4223

    BF> I see there's a file with that filename in qfiles/bad which
    BF> seems to be spam sent to mailman-owner.

    BF> Questions - should I be worried about the "lost data files"
    BF> message?  - is there a 'proper' way to deal with this message,
    BF> or can I just rm the file?

    BF> I get a lot of spam sent to mailman-owner, so seems likely
    BF> I'll get a few of these...

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.

Legit mail should almost never be unparseable.  Even broken mail
readers (yes they're out there ;) should be able to get message that
are close.  Mailman can parse messages are only slightly broken, but
some are just hosed beyond repair.  Those are the bad messages, and
they've always been spam IME.

-Barry