problems with mailman 2.0.12 qrunner failing to process any messages
Hi folks,
First off thanks for making such a great package.
I've been using mailman for a few years now to run mailing lists for various open source informatics efforts like biojava.org, biopython.org and bioperl.org.
We upgraded to 2.0.12 over the weekend and are now having trouble with mailman. It's basically stopped processing incoming email.
From looking at google and various mailing man list archives it seems that my problem is very similar to what some people saw in v2.06 with mailman not being able to gracefully handle some error or bounce situations. The patches discussed however seem to be already in place with mailman 2.0.12 (specifically a change to Boucers/DSN.py).
Right now I'm manually moving .msg and .db files into and out of the qfiles directory so that I can at least get some mail out. This will hopefully also give me a small sample of "bad" emails that are triggering the problem.
I'm not a python person so I'd appreciate any tips on how to resolve this. Here are the specifics:
qrunner is bombing out with an error and leaving lots of unprocessed messages in the qfiles/ directory. The output from the 'error' logfile is as follows:
[mailman@pw600a ~/qfiles]$ tail ../logs/error Jul 23 11:10:01 2002 qrunner(8882): Traceback (innermost last): Jul 23 11:10:01 2002 qrunner(8882): File "/home/mailman/cron/qrunner", line 283, in ? Jul 23 11:10:01 2002 qrunner(8882): kids = main(lock) Jul 23 11:10:01 2002 qrunner(8882): File "/home/mailman/cron/qrunner", line 253, in main Jul 23 11:10:01 2002 qrunner(8882): keepqueued = dispose_message(mlist, msg, msgdata) Jul 23 11:10:01 2002 qrunner(8882): File "/home/mailman/cron/qrunner", line 157, in dispose_message Jul 23 11:10:01 2002 qrunner(8882): mlist.ParseMailCommands(msg) Jul 23 11:10:01 2002 qrunner(8882): File "/home/mailman/Mailman/MailCommandHandler.py", line 123, in ParseMailCommands Jul 23 11:10:01 2002 qrunner(8882): precedence = msg.get('precedence', '').lower() Jul 23 11:10:01 2002 qrunner(8882): AttributeError : 'string' object has no attribute 'lower
Regards, Chris
-- Chris Dagdigian, <dag@sonsorol.org> Independent life science IT & research computing consulting Office: 617-666-6454, Mobile: 617-877-5498, Fax: 425-699-0193 Work: http://BioTeam.net PGP KeyID: 83D4310E Yahoo IM: craffi
Following up on my own email to continue the thread....
After isolating 14 messages and moving them out of the qfiles/ directory I was able to manually run qrunner and get my 412+ delayed mailing list messages. The process basically involved:
(1) manually running qmail until it fails (2) move the offending .msg and .db file out of qfiles/ (3) manually run qmail until it fails (4) move the offending .msg and .sb file out of qfiles/ (5) repeat cycle until qfiles/ is empty
The most interesting thing that I've learned is that almost all of the messages (.msg and .db) files that I had to manually move out of the qfiles directory are actually email replies from people using the subscription-confirmation process.
I'm going to wait until mail traffic dies down on the server and will then experiment to confirm that the Mailman confirmation email replies are causing qrunner to fail with a python traceback.
-Chris
[mailman@pw600a ~/qfiles]$ tail ../logs/error Jul 23 11:10:01 2002 qrunner(8882): Traceback (innermost last): Jul 23 11:10:01 2002 qrunner(8882): File "/home/mailman/cron/qrunner", line 283, in ? Jul 23 11:10:01 2002 qrunner(8882): kids = main(lock) Jul 23 11:10:01 2002 qrunner(8882): File "/home/mailman/cron/qrunner", line 253, in main Jul 23 11:10:01 2002 qrunner(8882): keepqueued = dispose_message(mlist, msg, msgdata) Jul 23 11:10:01 2002 qrunner(8882): File "/home/mailman/cron/qrunner", line 157, in dispose_message Jul 23 11:10:01 2002 qrunner(8882): mlist.ParseMailCommands(msg) Jul 23 11:10:01 2002 qrunner(8882): File "/home/mailman/Mailman/MailCommandHandler.py", line 123, in ParseMailCommands Jul 23 11:10:01 2002 qrunner(8882): precedence = msg.get('precedence', '').lower() Jul 23 11:10:01 2002 qrunner(8882): AttributeError : 'string' object has no attribute 'lower
"CD" == Chris Dagdigian <dag@sonsorol.org> writes:
CD> We upgraded to 2.0.12 over the weekend and are now having
CD> trouble with mailman. It's basically stopped processing
CD> incoming email.
CD> From looking at google and various mailing man list archives
CD> it seems that my problem is very similar to what some people
CD> saw in v2.06 with mailman not being able to gracefully handle
CD> some error or bounce situations. The patches discussed however
CD> seem to be already in place with mailman 2.0.12 (specifically
CD> a change to Boucers/DSN.py).
CD> Right now I'm manually moving .msg and .db files into and out
CD> of the qfiles directory so that I can at least get some mail
CD> out. This will hopefully also give me a small sample of "bad"
CD> emails that are triggering the problem.
CD> I'm not a python person so I'd appreciate any tips on how to
CD> resolve this. Here are the specifics:You're likely using Python 1.5.2. This is exactly the incompatibility fixed in the MM 2.0.13 candidate patch.
-Barry
Last night I patched my 2.0.12 distribution with the patch shown in this email:
http://mail.python.org/pipermail-21/mailman-developers/2002-July/012476.html
It worked wonderfully -- all mail including the ones that caused qrunner to stop have all been processed fine. No errors at all in the logs as of this morning.
So- consider this at least 1 success story for python1.5.2 and MM2.0.12.
Much appreciated!
Chris
Barry A. Warsaw wrote:
You're likely using Python 1.5.2. This is exactly the incompatibility fixed in the MM 2.0.13 candidate patch.
-Barry
-- Chris Dagdigian, <dag@sonsorol.org> Independent life science IT & research computing consulting Office: 617-666-6454, Mobile: 617-877-5498, Fax: 425-699-0193 Work: http://BioTeam.net PGP KeyID: 83D4310E Yahoo IM: craffi
"CD" == Chris Dagdigian <dag@sonsorol.org> writes:
CD> Last night I patched my 2.0.12 distribution with the patch
CD> shown in this email:
CD> http://mail.python.org/pipermail-21/mailman-developers/2002-July/012476.html
CD> It worked wonderfully -- all mail including the ones that
CD> caused qrunner to stop have all been processed fine. No errors
CD> at all in the logs as of this morning.
CD> So- consider this at least 1 success story for python1.5.2 and
CD> MM2.0.12.
CD> Much appreciated!Cool, thanks. -Barry
participants (2)
-
barry＠python.org -
Chris Dagdigian