Traceback rebuilding archive

Bug #265711 reported by Stdivjak on 2002-08-12
Affects Status Importance Assigned to Milestone
GNU Mailman

Bug Description

Witn Mailman 2.1b3, rebuilding a pipermail archive using
$ bin/arch listname
runs fine for 2 lists, but on the third one gives the
following traceback:

Updating HTML for article 52
Updating HTML for article 53
Schreibe Archivzustand in Datei
Traceback (most recent call last):
  File "bin/arch", line 160, in ?
  File "bin/arch", line 148, in main
    archiver.processUnixMailbox(fp, Article, start, end)
  File "/home/mailman/Mailman/Archiver/",
line 545, in processUnixMailbox
    m =
  File "/usr/local/lib/python2.2/", line 34, in
    return self.factory(_Subfile(self.fp, start, stop))
  File "/home/mailman/Mailman/", line 69, in
    return mailbox.scrub(msg)
  File "/home/mailman/Mailman/", line 89, in
    return self._scrubber(self._mlist, msg)
  File "/home/mailman/Mailman/Handlers/",
line 159, in process
  File "/home/mailman/Mailman/", line 76, in _
    return _translation.gettext(s) % dict
UnicodeError: ASCII decoding error: ordinal not in


Barry Warsaw (barry) wrote :

Can you upload the .mbox file for the list you're
regenerating? If not (perhaps because it's proprietary
information), can you make it available for me to look at

Barry Warsaw (barry) wrote :

I'm moving the bug report to pending since I haven't seen an
update. I suspect this is fixed in current cvs.

Stdivjak (stdivjak) wrote :

Sorry for the long delay. I fiddled around with the 19MB
mbox file, and cut out the part which causes this error
(refer to the attached file).

The traceback also appeared using 2.1b5.

Stdivjak (stdivjak) wrote :

Just tried to rebuild the other archives: 4 of 21 mbox-files
can't be rebuilt. There are two kinds of tracebacks:

* "ASCII decoding error" (see above)
* "Lookup error: unknown encoding"

I'll send the archive causing the second kind of traceback
to Barry, hence it contains somewhat internal information.

Barry Warsaw (barry) wrote :

Thanks Stefan,

I got your mbox file, which appeared to contain one message.
 That message has an unknown charset in its RFC 2047 Subject
header. Mailman cvs seems to handle this file just fine, so
I'm closing this as fixed in 2.1b5+

Stdivjak (stdivjak) wrote :

Barry told me, that it is fixed in the current CVS version in
September 2002, but this bug still appears in mailman
2.1.1 (using bin/arch on the attached mbox-file), so I
switched the status to open again.

Stdivjak (stdivjak) wrote :


- open the mbox-File in any Editor
- search for "*="
- replace iso-encoded MIME-fields 'name*' and 'filename*'
by plain text, removing the asterisk:
-> name="Autobahngebuehr.jpg"

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers