On 5/5/22 08:02, Pierre Malard via Mailman-users wrote:
Unfortunately we still don't have any archives...
Here are the logs retrieved from the mailman.log logs: May 05 15:59:42 2022 (579075) Exception in the HyperKitty archiver: {"error": "character with byte sequence 0xe2 0x80 0x99 in encoding \"UTF8\" has no equivalent in encoding \"LATIN1\"\n"} raise ValueError(result.text) ValueError: {"error": "character with byte sequence 0xe2 0x80 0x99 in encoding \"UTF8\" has no equivalent in encoding \"LATIN1\"\n"}
And in mailman-web.log: WARNING 2022-05-05 13:58:52,996 579167 hyperkitty.views.mailman Could not archive the email with message-id '<C7E61653-D399-466A-BEC3-CE61D567E870@teledetection.fr>': character with byte sequence 0xe2 0x80 0x99 in encoding "UTF8" has no equivalent in encoding "LATIN1"
Is it a way?
I don't understand the message about LATIN1. It seems to me that UTF-8 was the encoding retained in Mailman.
I too don't understand what's trying to encode as LATIN1. The particular byte sequence is a utf-8 encoding of right single quote (’) which has no LATIN1 equivalent, but there's not enough info in the logs for me to determine exactly what's going on.
There is an issue with MySQL and derivatives if that's the database you are using. You need the MySQL encoding to be UTF8MB4. in the DATABASES definition in your django settings you want
'OPTIONS': {'charset': 'utf8mb4'} # Enable utf8 4-byte encodings.
but that doesn't seem to be the issue here.
I suspect this issue has to do with the particular message. When mailman-hyperkitty processes the queue and a queued message throws an exception, it just dies. You might try moving aside the first (in alphanumeric sequence) message in /var/lib/mailman3/archives/hyperkitty/spool and see if the remaining messages can be processed. If that works I would like to see that message's .pck file.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan