
I'm running Mailman 2.1.5 on a Debian 3.1 box. In the last few days, I'm getting an increasing number of messages shunted, with error logs that look like:
Jan 30 23:10:53 2007 (3315) Uncaught runner exception: decoding Unicode is not supported Jan 30 23:10:53 2007 (3315) Traceback (most recent call last): File "/var/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/var/lib/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/lib/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/var/lib/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 91, in process send_digests(mlist, mboxfp) File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests msg = scrubber(mlist, msg) File "/var/lib/mailman/Mailman/Handlers/Scrubber.py", line 318, in process partcharset = part.get_content_charset() File "email/Message.py", line 800, in get_content_charset TypeError: decoding Unicode is not supported
Jan 30 23:10:53 2007 (3315) SHUNTING: 1170193244.4528749+524dabeddb1737e4b548d3ad0d7c3d9bd2c7c1a0
I have no idea why messages might have unicode in them.
This machine has the following python modules:
python-central 0.5.12 python-minimal 2.4.4-1 python2.3 2.3.5-16 python2.4 2.4.4-1 python2.4-minimal 2.4.4-1
I'm not aware of any config changes that have been made to this machine recently.
Two questions:
How do I get the shunted messages cleared? What has to happen before I run unshunt?
What do I need to do to clear the problem that is causing shunting?
Smith
Composed by sacbeemail. Get Your Free E-mail at http://www.sacbeemail.com . Or visit Northern Californias premiere news and information website at http://www.sacbee.com .

NFN Smith wrote:
I'm running Mailman 2.1.5 on a Debian 3.1 box. In the last few days, I'm getting an increasing number of messages shunted, with error logs that look like:
Jan 30 23:10:53 2007 (3315) Uncaught runner exception: decoding Unicode is not supported Jan 30 23:10:53 2007 (3315) Traceback (most recent call last): File "/var/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/var/lib/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued =3D self._dispose(mlist, msg, msgdata) File "/var/lib/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more =3D self._dopipeline(mlist, msg, msgdata, pipeline) File "/var/lib/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 91, in process send_digests(mlist, mboxfp) File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests msg =3D scrubber(mlist, msg) File "/var/lib/mailman/Mailman/Handlers/Scrubber.py", line 318, in process partcharset =3D part.get_content_charset() File "email/Message.py", line 800, in get_content_charset TypeError: decoding Unicode is not supported
Jan 30 23:10:53 2007 (3315) SHUNTING: 1170193244.4528749+524dabeddb1737e4b548d3ad0d7c3d9bd2c7c1a0
I believe you'll find the underlying problem is that there is a message in /var/lib/mailman/lists/<listname>/digest.mbox with a Content-Type: header with a charset="Unicode" parameter. If you edit the dgest.mbox file (possibly changing charset="Unicode" to charset="utf-8" or deleting the offending message), that will allow the list to resume processing.
As to which <listname>, it's the one that hasn't produced a digest since this started.
Two questions:
- How do I get the shunted messages cleared? What has to happen before I run unshunt?
Fix the digest.mbox (or just move it aside)
- What do I need to do to clear the problem that is causing shunting?
See 1).
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

Mark Sapiro wrote:
NFN Smith wrote:
- What do I need to do to clear the problem that is causing shunting?
See 1).
Note: if you meant what do you need to do to prevent this from happening again, upgrade to Mailman 2.1.7 or later.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro
-
NFN Smith