I made the big mistake of upgrading mailman a few days before going away for most of a week. Of course it all went strange whilst I was away (or more accurately the strangeness became significantly noticeable).
What appears to have been happening since a few days following the
upgrade from 2.0b2 to 2.0b4 is that the Yahoo Bouncer module started
throwing exceptions, which blocked a whole lot of mail in the queue.
Some mail went through without any apparent problems, other mail got
blocked. For example, digest messages generated on the daily digest
flush went out OK, but ones generated due to mail volume (ie
asynchronously generated), got stuck in the queue.
The error message generated was qrunner(16931): Traceback (innermost last): qrunner(16931): File "/home/mailman/cron/qrunner", line 209, in ? qrunner(16931): kids = main(lock) qrunner(16931): File "/home/mailman/cron/qrunner", line 178, in main qrunner(16931): keepqueued = dispose_message(mlist, msg, msgdata) qrunner(16931): File "/home/mailman/cron/qrunner", line 68, in dispose_message qrunner(16931): if BouncerAPI.ScanMessages(mlist, mimemsg): qrunner(16931): File "/home/mailman/Mailman/Bouncers/BouncerAPI.py", line 54, in ScanMessages qrunner(16931): addrs = func(msg) qrunner(16931): File "/home/mailman/Mailman/Bouncers/Yahoo.py", line 31, in process qrunner(16931): if string.lower(msg.get('from')) <> 'mailer-daemon@yahoo.com':
I twiddled Yahoo.py slightly but couldn't quite see the problem, so finally removed it from the Bounce API stuff, and the queue then unblocked itself.
Nigel.-- [ - Opinions expressed are personal and may not be shared by VData - ] [ Nigel Metheringham Nigel.Metheringham@VData.co.uk ] [ Phone: +44 1423 850000 Fax +44 1423 858866 ]