[Mailman-Users] unknown encoding crashes qrunner
ifetch at du.edu
Thu Oct 6 19:04:59 CEST 2005
Hi Stephen - thanks for replying!
In your experience, has this stopped Mailman from processing incoming
messages? After soem further investigation, I've seen these same errors
take place, yet Mailman continues processing messages. This makes me
wonder if what ever is affecting qrunner(s) isn't something else...
On Thu, 6 Oct 2005, Stephen J. Turnbull wrote:
>>>>>> "Ivan" == Ivan Fetch <ifetch at du.edu> writes:
> Ivan> I'm confused as to why the unknown encoding is "unknown" -
> Ivan> can someone shed light on this?
> Probably because some less-than-conformant agent put that literal
> string in a Content-Type header. Try grepping the spool for
> "charset=unknown" (or just "unknown") and look carefully at the
> message found. I've seen that "charset" in spam messages (at least).
> BTW, from Mailman's (actually, Mailman just passes the buck to Python)
> point of view, it's unknown because there is no codec (character
> encoder/decoder modules) for a charset named "unknown". You'd run
> into the same thing if the charset were, say, "hellspark". I get this
> kind of thing all the time (in a different Python application) because
> Mac OS X defaults to "X-Mac-Japanese" in my locale. :-(
> School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
> University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
> Ask not how you can "do" free software business;
> ask what your business can "do for" free software.
More information about the Mailman-Users