[Mailman-Users] trouble after security upgrade

[Patrick Lesslie]

I apologise if this has been covered recently.

Recently I upgraded mailman running on Debian stable to meet a
security upgrade.  A couple of days later I noticed that posts
weren't appearing, and "help" to -request wasn't being answered.

I downgraded again and all the messages came through, with none
lost or unanswered.  The messages hadn't been in the exim queue,
so mailman must have queued them.

Errors like this were repeated in /var/log/mailman/error:

Feb 11 05:47:05 2004 qrunner(19980): Traceback (most recent call last):
Feb 11 05:47:05 2004 qrunner(19980):   File "/usr/lib/mailman/cron/qrunner", line 283, in ?
Feb 11 05:47:05 2004 qrunner(19980):      kids = main(lock)
Feb 11 05:47:05 2004 qrunner(19980):   File "/usr/lib/mailman/cron/qrunner", line 253, in main
Feb 11 05:47:05 2004 qrunner(19980):      keepqueued = dispose_message(mlist, msg, msgdata)
Feb 11 05:47:05 2004 qrunner(19980):   File "/usr/lib/mailman/cron/qrunner", line 157, in dispose_message
Feb 11 05:47:05 2004 qrunner(19980):      mlist.ParseMailCommands(msg)
Feb 11 05:47:05 2004 qrunner(19980):   File "/usr/lib/mailman/Mailman/MailCommandHandler.py", line 163, in ParseMailCommands
Feb 11 05:47:09 2004 qrunner(19980):      splitsubj = string.split(subject)
Feb 11 05:47:09 2004 qrunner(19980):   File "/usr/lib/python2.1/string.py", line 114, in split
Feb 11 05:47:09 2004 qrunner(19980):      return s.split(sep, maxsplit)
Feb 11 05:47:09 2004 qrunner(19980): AttributeError :  'None' object has no attribute 'split' 

Since I downgraded it's been fine.  The upgrade was from
2.0.11-1woody5 to 2.0.11-1woody7.  I'd like to upgrade but of course
I'd like to avoid this problem.  Should I be stopping some processes
first?

Thanks,
Patrick Lesslie