Apr 10 03:19:57 2002 (12285) message is unparsable: 1018423196.419311+a81685d7af 1f6631ce6392a83aff01fde476543f Apr 10 03:19:57 2002 (12285) lost data files for filebase: 1018423196.419311+a81 685d7af1f6631ce6392a83aff01fde476543f
I don't mind the unparseability so much as the fact that it lost the files, so now I can't see *why* it was unparseable...
Based on the syslog, I see which one it must have been. Looks like it was spam anyway, so hopefully it was just their spamming package mangling the message.
"RJ" == Ron Jarrell <jarrell@vt.edu> writes:
RJ> Apr 10 03:19:57 2002 (12285) message is unparsable:
RJ> 1018423196.419311+a81685d7af 1f6631ce6392a83aff01fde476543f
RJ> Apr 10 03:19:57 2002 (12285) lost data files for filebase:
RJ> 1018423196.419311+a81 685d7af1f6631ce6392a83aff01fde476543f
RJ> I don't mind the unparseability so much as the fact that it
RJ> lost the files, so now I can't see *why* it was unparseable...
RJ> Based on the syslog, I see which one it must have been. Looks
RJ> like it was spam anyway, so hopefully it was just their
RJ> spamming package mangling the message.Set QRUNNER_SAVE_BAD_MESSAGES = 1 in your mm_cfg.py file and the unparseable messages will be left in qfiles/bad/*.txt.
I agree it was likely spam because (most) legit mail is promerly MIME chromed. I'm not psyched about trying harder to parse or handle legitimate, but incorrectly MIME chromed messages. :/
-Barry
At 01:41 AM 5/6/02 -0400, Barry A. Warsaw wrote:
"RJ" == Ron Jarrell <jarrell@vt.edu> writes:
RJ> Apr 10 03:19:57 2002 (12285) message is unparsable: RJ> 1018423196.419311+a81685d7af 1f6631ce6392a83aff01fde476543f RJ> Apr 10 03:19:57 2002 (12285) lost data files for filebase: RJ> 1018423196.419311+a81 685d7af1f6631ce6392a83aff01fde476543f
RJ> I don't mind the unparseability so much as the fact that it RJ> lost the files, so now I can't see *why* it was unparseable...
RJ> Based on the syslog, I see which one it must have been. Looks RJ> like it was spam anyway, so hopefully it was just their RJ> spamming package mangling the message.
Set QRUNNER_SAVE_BAD_MESSAGES = 1 in your mm_cfg.py file and the unparseable messages will be left in qfiles/bad/*.txt.
Actually, I *had* set it. Other messages since then have been properly dumped into the file -- and each of them has been a virus that wasn't parseable. Gee, I consider that a feature :-). That one, for some reason, just vanished into thin ether.
participants (2)
-
barry＠zope.com -
Ron Jarrell