Hello,
Every few days now I've been getting spam that crashes tmda-pending.
Here's now it fails:
[EMAIL PROTECTED]> tmda-pending 1057389239.69406.msg
Traceback (most recent call last):
File "/usr/local/bin/tmda-pending", line 311, in ?
main()
File "/usr/local/bin/tmda-pending", line 304, in main
q.mainLoop()
File "/usr/local/lib/python2.2/site-packages/TMDA/Pending.py", line 295, in mainLoop
if not self.processMessage(M):
File "/usr/local/lib/python2.2/site-packages/TMDA/Pending.py", line 359, in
processMessage
self.showMessage(M)
File "/usr/local/lib/python2.2/site-packages/TMDA/Pending.py", line 258, in
showMessage
self.Print(M.summary(self.count, self.total, self.summary))
File "/usr/local/lib/python2.2/site-packages/TMDA/Pending.py", line 566, in summary
str += "%s %s: %s\n" % (' >>',
File "/usr/local/lib/python2.2/site-packages/TMDA/Util.py", line 581, in
decode_header
pairs = Header.decode_header(str)
File "/usr/local/lib/python2.2/site-packages/TMDA/pythonlib/email/Header.py", line
113, in decode_header
raise HeaderParseError
email.Errors.HeaderParseError
######
Here's an example spam that will do this:
http://mark.stosberg.com/misc/1057389239.69406.msg
#####
Are other people experiencing this? Suggested work-arounds or fixes?
Thinking in Perl terms, the solution would be wrap this part of the code
in an "eval" statement, so even if the parser died, tmda-pending could
die more gracefully, and just skip the message with a note that it's
unparsable.
Perhaps this is all Asian spam that I should be filtering pre-TMDA
anyway.
Mark
--
. . . . . . . . . . . . . . . . . . . . . . . . . . .
Mark Stosberg Principal Developer
[EMAIL PROTECTED] Summersault, LLC
765-939-9301 ext 202 database driven websites
. . . . . http://www.summersault.com/ . . . . . . . .
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
