[Mailman-Developers] bin/arch problems with unknown encodings

Andrew D. Clark andrew.clark@ucsb.edu
Wed Nov 20 18:35:29 2002

Under Mailman 2.1b5, when I run bin/arch on one of my lists for which I 
turned off pipermail archiving during the 
2.1b3-pipermail-archiving-performance-sucks-badly period it dies 
"unknown encoding: big5_tw".

The mbox for this list is huge, and I'm having trouble locating exactly 
which message is killing arch.  Is there a way to either ignore non 
us-ascii messages when archiving (all the members of this private list only 
speak/read English, I'm not simply another arrogant American :) ), or a 
better way to scrub or locate such messages?  I'm having similar problems 
with some other lists:
"TypeError: unicode() argument 2 must be string, not None"

BTW, I skipped Mailman 2.1b4 completely, so would running b4b5-archfix 
still be necessary/beneficial?
BTW2, kudos to the cabal on 2.1b5!  An older list archive created under 
mailman 2.0.x reported 20 messages in the archive, when I regenerated that 
list archive, the new archive reported 16.  A manual peek at the mbox file 
showed 16 messages :)

Andrew Clark
Campus Network Programmer
Office of Information Technology
University of California, Santa Barbara
andrew.clark@ucsb.edu (805) 893-5311

More information about the Mailman-Developers mailing list