[Mailman-Users] UnicodeDecodeError with Mailman 2.1 and Python 2.6

[David Magda]

On Tue, September 1, 2015 13:53, Mark Sapiro wrote:

> There shouldn't be any non-ascii in a mbox. Well, maybe in a
> "Content-Transfer-Encoding: 8bit" (or binary?) body part, but certainly
> not in any headers.
>
> I don't know what you are grepping, but if it's the mbox, you shouldn't
> be looking for "\xea", you should be looking for "ê".

Yes, there are a number of messages with a C-T-E of 8bit.

> Are you running bin/arch with the --wipe option? If not, you are
> repeatedly adding the same messages to the archive which is why the
> number increases.

Doing a run with "--wipe" seems to have fixed things. Doing a complete
're-build' (from message 0) finished without errors, and sending a test
message seems to have now generated a proper archive HTML page for
September 2015. Previously the last archive web page was for a message
sent August 25, even though a few messages had come between then and now.

Could the new version of Python been chocking on a binary file whose
format has changed from the old version? Is it prudent to do an "arch
--wipe" when changing versions of Python?