[Spambayes] Spambayes failure on a message
kurtbuff at spro.net
Wed May 26 19:17:35 EDT 2004
I am using [SpamBayes POP3 Proxy Version 0.4 (February 2004)], with the
recommended (at that time) python installs.
This is the only failure I've seen of this type since installing it, so
you might very well be prudent to not worry much about it. If I get a
bunch more like this, I'll let the list know.
From: Tony Meyer [mailto:tameyer at ihug.co.nz]
Sent: Wednesday, May 26, 2004 16:05
To: kurtbuff at spro.net; spambayes at python.org
Subject: RE: [Spambayes] Spambayes failure on a message
> The message included as an attachment was found in my inbox.
> I found the following set of SpamBayes headers on it:
> ----------begin snip----------
> X-Spambayes-Exception: Traceback (most recent call last):
> . File "sb_server.pyc", line 446, in onRetr
> . File "spambayes\message.pyc", line 243, in setPayload
> . File "email\Parser.pyc", line 245, in _parsebody
> .BoundaryError: multipart message with no defined boundary
> ----------end snip----------
Are you using the binary, or source? If source, what version of Python?
The message parses fine for me, although I can see that it's malformed.
If a lot of messages with a particular malformation arrive (like the
spate of ones that generated TypeErrors) then we can add in code to deal
with them, but if there are just a few it's not really worth it. In the
longer term we'll be using the newer Python email package which handles
malformed mail much nicer, and that should eliminate almost all these
problems (we'll build the binaries with it, and source users can update
it, or we might possibly bundle it). It's not really worth duplicating
Barry/Anthony's work there to fix all the problems here (since we do at
least catch the error rather than die - so you could treat all messages
a "X-SpamBayes-Exception" header as unsure).
More information about the Spambayes