[Mailman-Users] Mailman just stopped
msapiro at value.net
Thu Sep 21 22:36:59 CEST 2006
>Mailman has been working beautifully for awhile now but yesterday it just stopped. I wound up repairing all of the databases but it happened again today. I'm getting the following error:
>Sep 21 06:11:17 2006 (15075) Uncaught runner exception: unknown encoding: gb2312
>Sep 21 06:11:17 2006 (15075) Traceback (most recent call last):
> File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop
> self._onefile(msg, msgdata)
> File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in _onefile
> keepqueued = self._dispose(mlist, msg, msgdata)
> File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose
> more = self._dopipeline(mlist, msg, msgdata, pipeline)
> File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline
> sys.modules[modname].process(mlist, msg, msgdata)
> File "/usr/share/mailman/Mailman/Handlers/CookHeaders.py", line 74, in process
> prefix_subject(mlist, msg, msgdata)
> File "/usr/share/mailman/Mailman/Handlers/CookHeaders.py", line 262, in prefix_subject
> h.append(s, c)
> File "/BinaryCache/mailman/mailman-117.root~35/usr/share/mailman/pythonlib/email/Header.py", line 285, in append
>LookupError: unknown encoding: gb2312
>Sep 21 06:11:17 2006 (15075) SHUNTING: 1158844276.9904189+1e2464070413bcc3355b914153a142061eb60c6f
>Does anyone know what might be causing this and why it would happen suddenly like this.
There are several things going on here. A message (most likely spam) is
being posted to your list and accepted for delivery. This message has
it's Subject: header encoded in the 'gb2312' (chinese) character set.
Mailman is trying to decode the Subject: so it can add the
subject_prefix and your Mailman/Python installation does not
support/recognize the 'gb2312' character set.
The above error occurs and the message is moved to Mailman's shunt
queue where it will stay untouched until you manually remove it or
queue it for reprocessing using bin/unshunt.
You can use bin/show_qfiles or bin/dumpdb to look at the entries in
qfiles/shunt and then just remove those you don't want.
You can also adjust your list settings to be not so generous in what
There is something wrong with your Mailman installation as it should
This specific error should not stop Mailman. It just shunts the message
and that should be the end of it.
Mark Sapiro <msapiro at value.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
More information about the Mailman-Users