[ mailman-Bugs-726736 ] qrunner hung by spam

SourceForge.net noreply at sourceforge.net
Sun Jan 4 10:54:17 EST 2004


Bugs item #726736, was opened at 2003-04-24 10:01
Message generated for change (Comment added) made by ber
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726736&group_id=103

Category: mail delivery
Group: 2.0.x
Status: Open
Resolution: None
Priority: 8
Submitted By: Greg Lindahl (greglindahl)
Assigned to: Nobody/Anonymous (nobody)
Summary: qrunner hung by spam

Initial Comment:
I realized no mail had gone out for 6 days, and saw
that qrunner was barfing on SOMETHING. This is with
Mailman 2.0.6. Even
though I'm behind the times, I'd bet this bug could be
in 2.1.X -- I just don't know enough Python to see
what's going on. I blew away a bunch of files in my
qfiles directory; I didn't save the bad message.

Apr 24 00:39:01 2003 qrunner(2397): Traceback
(innermost last):
Apr 24 00:39:01 2003 qrunner(2397):   File
"/home/mailman/cron/qrunner", line 282, in ?
Apr 24 00:39:01 2003 qrunner(2397):      kids = main(lock)
Apr 24 00:39:01 2003 qrunner(2397):   File
"/home/mailman/cron/qrunner", line 252, in main
Apr 24 00:39:01 2003 qrunner(2397):      keepqueued =
dispose_message(mlist, msg, msgdata)
Apr 24 00:39:01 2003 qrunner(2397):   File
"/home/mailman/cron/qrunner", line 121, in dispose_message
Apr 24 00:39:01 2003 qrunner(2397):      if
BouncerAPI.ScanMessages(mlist, mimemsg):
Apr 24 00:39:01 2003 qrunner(2397):   File
"/home/mailman/Mailman/Bouncers/BouncerAPI.py", line
59, in ScanMessages
Apr 24 00:39:01 2003 qrunner(2397):      addrs = func(msg)
Apr 24 00:39:01 2003 qrunner(2397):   File
"/home/mailman/Mailman/Bouncers/Postfix.py", line 39,
in process
Apr 24 00:39:01 2003 qrunner(2397):      more =
mfile.next()
Apr 24 00:39:01 2003 qrunner(2397):   File
"/usr/lib/python1.5/multifile.py", line 121, in next
Apr 24 00:39:01 2003 qrunner(2397):      while
self.readline(): pass
Apr 24 00:39:01 2003 qrunner(2397):   File
"/usr/lib/python1.5/multifile.py", line 93, in readline
Apr 24 00:39:01 2003 qrunner(2397):      if marker ==
self.section_divider(sep):
Apr 24 00:39:01 2003 qrunner(2397):   File
"/usr/lib/python1.5/multifile.py", line 157, in
section_divider
Apr 24 00:39:01 2003 qrunner(2397):      return "--" + str
Apr 24 00:39:01 2003 qrunner(2397): TypeError : 
illegal argument type for built-in operation


----------------------------------------------------------------------

Comment By: Bernhard Reiter (ber)
Date: 2004-01-04 16:54

Message:
Logged In: YES 
user_id=113859

Greg, maybe you should close the bug
in addition to send another email to the mailman lists
to ask for an 2.0.14 release.
An alternative would be to make a patch release,
this bug certainly is critical for 2.0.x.
On the other hand it most likely does not affect 2.1.x.

----------------------------------------------------------------------

Comment By: Greg Lindahl (greglindahl)
Date: 2003-08-06 02:13

Message:
Logged In: YES 
user_id=612574

Thanks -- I see that you fixed all of them in your patch.

This should be added to the 2.0.X series.


----------------------------------------------------------------------

Comment By: Bernhard Reiter (ber)
Date: 2003-08-05 19:41

Message:
Logged In: YES 
user_id=113859

I've submitted a patch for this to the patch tracker 783651
https://sourceforge.net/tracker/index.php?func=detail&aid=783651&group_id=103&atid=300103


----------------------------------------------------------------------

Comment By: Bernhard Reiter (ber)
Date: 2003-08-05 19:32

Message:
Logged In: YES 
user_id=113859

I also encountered that bug once at a site of a friend.
Take a look at Mailman/Bouncers/Postfix.py
and especially the line with
       boundary = msg.getparam('boundary')
this can result in boundary being "None" 
which is then not treated properly.
So add the following check below this with
the correct indentation:
        if not boundary:
                        return None


If I remember correctly this was handled completely differently
in Mailman 2.1 so I believe that this bug is limited to
Mailman 2.0.x.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726736&group_id=103



More information about the Mailman-coders mailing list