[Mailman-Users] Mailman just died

[Jon Carnes]

Seems like it's looking at the subject line of a message in the queue
and failing.  Could be a corrupt Subject in a message, or a message
crafted by a bogus robot that spews out some bad characters on the
Subject line... 

I suggest that you look at the files in your Mailman queue and look at
the oldest queued file.  See if there is anything odd about the subject.
If so, then move that file out of the queue directory and see if that
frees up the rest of the queue to move on.

You might want to simply move all the files out of the queue and then
send some test messages through. If the test messages go through, then
you've found your problem.

ASIDE: I'm assuming here that you are using the default (unpatched)
install of Mailman 2.0.13.

Good Luck - Jon Carnes

On Thu, 2003-10-09 at 03:13, Matt "TrollBoy" Wiseman wrote:
> I'm getting the following error every second... anyone know of a fix..
> it just started out of the blue..the list was working.  Its mailman
> version 2.0.13
> 
> Oct 09 01:00:01 2003 qrunner(59067): Traceback (most recent call last):
> Oct 09 01:00:01 2003 qrunner(59067):   File
> "/usr/local/mailman/cron/qrunner", line 283, in ?
> Oct 09 01:00:01 2003 qrunner(59067):      kids = main(lock)
> Oct 09 01:00:01 2003 qrunner(59067):   File
> "/usr/local/mailman/cron/qrunner", line 253, in main
> Oct 09 01:00:01 2003 qrunner(59067):      keepqueued =
> dispose_message(mlist, msg, msgdata)
> Oct 09 01:00:01 2003 qrunner(59067):   File
> "/usr/local/mailman/cron/qrunner", line 157, in dispose_message
> Oct 09 01:00:01 2003 qrunner(59067):      mlist.ParseMailCommands(msg)
> Oct 09 01:00:01 2003 qrunner(59067):   File
> "/usr/local/mailman/Mailman/MailCommandHandler.py", line 163, in
> ParseMailCommands
> Oct 09 01:00:01 2003 qrunner(59067):      if (subject and
> Oct 09 01:00:01 2003 qrunner(59067): IndexError :  list index out of
> range