exception (utf8 codec) in pipermail
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNU Mailman |
Incomplete
|
Undecided
|
Mark Sapiro |
Bug Description
After upgrading Mailman from 2.1.23 to 2.1.26-1 on Debian, things went smoothly,
the list's mbox is updated but the archives are not updated.
In the error log, one sees, for every message
Jun 23 19:59:03 2018 (20419) SHUNTING: 1529776742.
Jun 23 21:35:24 2018 (20419) Uncaught runner exception: 'utf8' codec can't decode byte 0xaa in position 26: invalid start byte
Jun 23 21:35:24 2018 (20419) Traceback (most recent call last):
File "/var/lib/
self.
File "/var/lib/
keepqueued = self._dispose(
File "/var/lib/
mlist.
File "/var/lib/
h.processUn
File "/var/lib/
self.
File "/var/lib/
author = fixAuthor(
File "/var/lib/
while i>0 and (L[i-1][0] in lowercase or
UnicodeDecodeError: 'utf8' codec can't decode byte 0xaa in position 26: invalid start byte
This is always the same complaint. I have checked shunted messages and the mbox itself
and I have not found any 0xaa value in them.
This may have something to do with the archive database. You can try the script at https:/ /www.msapiro. net/scripts/ hddump to dump the database for the affected period with --verbose and look for values of 'author' and 'decoded' ['author' ]. Is there anything unusual in those or anything with a number like 'Doe, John 3rd'.
If you can post one of the shunted message files or email it to <email address hidden> if you don't want to post it, I'll see if I can duplicate this, but also, please see https:/ /wiki.list. org/x/12812344 .