#473 Spam causes exception
The following message triggers an exception (see the
headers):
Received: from na-200-78-223-14.na.avantel.net.mx
([200.78.223.14]:43050 "HELO
na-200-78-223-14.na.avantel.net.mx") by
ps3.test.onet.pl with SMTP
id <S1353796AbUAOHRS>; Thu, 15 Jan 2004 08:17:18 +0100
Received: from mail[127.0.0.1] by
na-200-78-223-14.na.avantel.net.mx with ESMTP id
15724901; Thu, 15 Jan 2004 04:05:26 -0300
Message-ID: <8o5nh9t68c2q842-244@djt4s.n.0.21o>
From: "Gary Egan" <t021kub@bentcom.net>
Reply-To: "Gary Egan" <t021kub@bentcom.net>
To: dave_78@poczta.onet.pl
Subject: Get a Diploma without the hassle!
Date: Thu, 15 Jan 04 04:05:26 -0500
X-Mailer: eGroups Message Poster
MIME-Version: 1.0
Content-Type: multipart/alternative;
X-Priority: 3
X-MSMail-Priority: Normal
Content-Type: text/plain;
Content-Transfer-Encoding: quoted-printable
X-OrigFrom: t021kub@bentcom.net
Status: O
X-Spambayes-Exception: Traceback (most recent call last):
. File "/usr/bin/sb_server.py", line 438, in onRetr
. msg.setPayload(messageText)
. File
"/usr/lib/python2.3/site-packages/spambayes/message.py",
line 231,
in setPayload . prs._parsebody(self, fp)
. File "/usr/lib/python2.3/email/Parser.py", line
245, in _parsebody
. raise Errors.BoundaryError(
.BoundaryError: multipart message with no defined boundary
GET YOUR UNIVERSITY DIPLOMA OR GED
Do you want a prosperous future, increased earning
power more money and th=
e respect of all?
Call this number: 1-646-304-7539 (24 hours)
There are no required tests, classes, books, or interviews!
Get a Bachelors, Masters, MBA, GED and Doctorate (PhD)
diploma!
Receive the benefits and admiration that comes with a
diploma!
No one is turned down!
Call Today 1-646-304-7539 (7 days a week)
Confidentiality assured!
Logged In: YES
user_id=954793
I have also received this error:
X-Spambayes-Exception: Traceback (most recent call last):
. File "./sb_server.py", line 438, in onRetr
. msg.setPayload(messageText)
. File "/usr/lib/python2.3/site-packages/spambayes/message.py", line
180,
in setPayload . prs._parsebody(self, fp)
. File "/usr/lib/python2.3/email/Parser.py", line 245, in _parsebody
. raise Errors.BoundaryError(
.BoundaryError: multipart message with no defined boundary
Status: R
X-Status: N
X-KMail-EncryptionState:
X-KMail-SignatureState:
<html><body><center><u>Image Loading...........</u><br><a
href=3D"http://g=
etmyprize.com/ec/index.asp"><img border=3D"0" src=3D"http:
//getmyprize.com=
/ec/ec_spp.gif"></a><br><br><br><br><br><br><br><br><br><br><a
href=3D"htt=
p://getmyprize.com/rem.asp"><img border=3D"0" src=3D"http:
//getmyprize.com=
/gmp-rm.gif"><br><br></a></center></body></html>
-------
Logged In: YES
user_id=552329
The first 1.1 release will solve this problem, as it will be
built with Python 2.4, which handles parsing much better.
(Or if you run from source, you can solve it immediately by
using Python 2.4)
For the moment, the X-Spambayes-Exception header is probably
as good as it will get. There isn't much point trying to
work around all the possible malformations possible (this is
what Python 2.4's email package does, so we would be
duplicating work). The exception would be if there was a
huge flood of a particular type of malformed message, which
this doesn't appear to be.