[Mailman-Users] unknown encoding crashes qrunner
msapiro at value.net
Fri Oct 7 06:41:50 CEST 2005
Ivan Fetch wrote:
>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).
Actually, the originally posted error trace shows the error occurring
in CookHeaders.py in the attempt to add the subject prefix to the
subject header, so in this case, the 'unknown' character set would not
have been specified in a Content-Type: header, but rather in an RFC
2047 encoding of the message subject.
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