Hi Jared, I'm curious what kind of message caused this error. I think that the exact message causing this error contains a header like:
Content-Type: text/plain; charset=base64 It would be nice if you can check the moved digest.mbox and answer if my hyposis is right or not. Mark, I've checked in a patch for this error. Will you please review it and back out if it is not appropriate because I have not much time to spend now. Tokio Jared Nyland wote: > Hi Mark, > > I have found a fix for this issue. In the /var/lib/mailman/lists/listname, > I remane the digest.mbox then run the /bin/unshunt. It looks like it is > working now. > > > Thanks again for all your help > Jared > > > On 5/9/07, Jared Nyland <[EMAIL PROTECTED]> wrote: >> Hi Mark, >> >> Thanks for the help on this, I did try those but still does not work. In >> doing some more trouble shooting I have found that the message that I am >> sending is getting stuck in the shunt directory. I have also found in the >> mailman log file that I get this error. >> >> May 09 09:49:46 2007 (5607) Uncaught runner exception: >> May 09 09:49:46 2007 (5607) Traceback (most recent call last): >> File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 110, in _oneloop >> self._onefile(msg, msgdata) >> File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 160, in _onefile >> keepqueued = self._dispose(mlist, msg, msgdata) >> File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 130, in >> _dispose >> more = self._dopipeline(mlist, msg, msgdata, pipeline) >> File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 153, in >> _dopipeline >> sys.modules[modname].process(mlist, msg, msgdata) >> File "/usr/lib/mailman/Mailman/Handlers/ToDigest.py", line 91, in process >> >> send_digests(mlist, mboxfp) >> File "/usr/lib/mailman/Mailman/Handlers/ToDigest.py", line 132, in >> send_digests >> send_i18n_digests(mlist, mboxfp) >> File "/usr/lib/mailman/Mailman/Handlers/ToDigest.py", line 306, in >> send_i18n_digests >> msg = scrubber(mlist, msg) >> File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 304, in >> process >> t = unicode(t, partcharset, 'replace') >> File "/usr/lib/python2.3/encodings/base64_codec.py", line 41, in >> base64_decode >> assert errors == 'strict' >> AssertionError >> >> May 09 09:49:47 2007 (5607) SHUNTING: >> 1178725785.6627519+f5e2d81766111458741eb658164fc17d90bde0ab >> >> >> Thanks again >> Jared >> >> >> On 5/9/07, Mark Sapiro <[EMAIL PROTECTED]> wrote: >>> Jared Nyland wrote: >>>> I have run into a issues where mail has all of a sudden stopped being >>> sent >>>> to the mailing list. >>> >>> See >>> <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.078.htp>, >>> particularly items 5b, 6 and 7. >>> >>> Most likely, one or more of your qrunners isn't running and messages >>> are just waiting in Mailman's qfiles/in/ or qfiles/out/ queues. >>> >>> -- >>> Mark Sapiro <[EMAIL PROTECTED] > The highway is for gamblers, >>> San Francisco Bay Area, California better use your sense - B. Dylan >>> >>> -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ------------------------------------------------------ Mailman-Users mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
