Anil Jangity wrote: >error log shows this. How do I re-parse these messages? The digest.mbox files >are gone, as soon as I run into this error. where is it "preserving"? > > >Jan 22 14:13:32 2012 (10035) Uncaught runner exception: No module named header >Jan 22 14:13:32 2012 (10035) Traceback (most recent call last): > File "/gcs/app/mail/listsp/mailman/Mailman/Queue/Runner.py", line 100, in > _oneloop > msg, msgdata = self._switchboard.dequeue(filebase) > File "/gcs/app/mail/listsp/mailman/Mailman/Queue/Switchboard.py", line 160, > in dequeue > msg = cPickle.load(fp) >ImportError: No module named header > >Jan 22 14:13:32 2012 (10035) Skipping and preserving unparseable message: >1327270411.391972+7e77c4c48f3738aaa8ef44b5aa7ddb4176b7e2ac >Jan 22 14:13:32 2012 (10035) Uncaught runner exception: No module named header >Jan 22 14:13:32 2012 (10035) Traceback (most recent call last): > File "/gcs/app/mail/listsp/mailman/Mailman/Queue/Runner.py", line 100, in > _oneloop > msg, msgdata = self._switchboard.dequeue(filebase) > File "/gcs/app/mail/listsp/mailman/Mailman/Queue/Switchboard.py", line 160, > in dequeue > msg = cPickle.load(fp) >ImportError: No module named header > >Jan 22 14:13:32 2012 (10035) Skipping and preserving unparseable message: >1327270411.424971+ea345bed52b63ad4d2c02cec5964d2df915a4b43
The preserved messages are in qfiles/bad, but you have a major compatibility issue. I can't really tell in detail what's going on because the ImportError is thrown diring unpickling, but somehow the queue entry being processed by whatever runner this is has a reference to an email.header object, but the Python processing this is using an older email package that doesn't have that module, only email.Header. The most likely underlying issue is this is Python 2.5 or newer, but you have an older email package in Mailman's pythonlib. The email package in Mailman's pythonlib is not compatible with the rest of the Python library in any Python 2.5 or newer version. If Mailman 2.1.12 or later is properly configured and installed from source, it will detect that the system Python has an email package as new or newer than 2.5.8 and will not install its email package in pythonlib and will remove an existing pythonlib/email. It seems that perhaps what you have done is upgraded the Python in an older Mailman installation and not reconfigured Mailman. -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
