[Mailman-Developers] [ mailman-Bugs-649007 ] bin/arch crash: unknown encoding

noreply at sourceforge.net noreply at sourceforge.net
Thu Dec 5 15:35:56 2002

Bugs item #649007, was opened at 2002-12-05 10:21
You can respond by visiting: 

Category: None
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Greg Ward (gward)
Assigned to: Nobody/Anonymous (nobody)
>Summary: bin/arch crash: unknown encoding

Initial Comment:
bin/arch is crashing with the following traceback:

Updating HTML for article 27
Pickling archive state into /usr/local/mailman/archives/private/mems-talk/pipermail.pck
Traceback (most recent call last):
  File "./bin/arch", line 186, in ?
  File "./bin/arch", line 174, in main
    archiver.processUnixMailbox(fp, start, end)
  File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 557, in processUnixMailbox
    a = self._makeArticle(m, self.sequence)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 630, in _makeArticle
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 261, in __init__
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 354, in check_header_charsets
    author, a_charset = self.decode_charset(self.author)
  File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 383, in decode_charset
    h = make_header(pairs, 99999)
  File "/usr/local/mailman/pythonlib/email/Header.py", line 123, in make_header
    h.append(s, charset)
  File "/usr/local/mailman/pythonlib/email/Header.py", line 230, in append
    ustr = unicode(s, incodec)
LookupError: unknown encoding: gb2312

Oddly, it appears that the message causing the problem has no mention of gb2312 -- there are some bogus MIME headers in the body that mention big5, though.


Comment By: Greg Ward (gward)
Date: 2002-12-05 10:33

Logged In: YES 

Ahh!  Ignore my last paragraph: the offending message yesterday was one with "big5" mentioned in a MIME header.  The one causing problems today has 1) gb2312 in the Subject and 2) binary junk in a footer supplied by yahoo.com.cn.


You can respond by visiting: 

More information about the Mailman-Developers mailing list