On 9/9/25 14:47, Wikinaut wrote:
Mark,
my database **was** already on utf8mb.
Do you mean utf8mb4? I don't think there is a utf8mb encoding, but if there is it may be an alias for utf8mb3.
I checked with the server (with the problem) from which I moved to a new server, the sam issue. Server 1: SHOW FULL COLUMNS FROM hyperkitty_email; +-----------------+--------------+--------------------+------+-----+---------+----------------+---------------------------------+---------+ | Field | Type | Collation | Null | Key | Default | Extra | Privileges | Comment | +-----------------+--------------+--------------------+------+-----+---------+----------------+---------------------------------+---------+ | id | int(11) | NULL | NO | PRI | NULL | auto_increment | select,insert,update,references | | | message_id | varchar(255) | utf8mb4_general_ci | NO | MUL | NULL | | select,insert,update,references | | | message_id_hash | varchar(255) | utf8mb4_general_ci | NO | MUL | NULL | | select,insert,update,references | | | subject | varchar(512) | utf8mb4_general_ci | NO | MUL | NULL | | select,insert,update,references | | | content | longtext | utf8mb4_general_ci | NO | | NULL | | select,insert,update,references | | | date | datetime(6) | NULL | NO | MUL | NULL | | select,insert,update,references | | | timezone | smallint(6) | NULL | NO | | NULL | | select,insert,update,references | | | in_reply_to | varchar(255) | utf8mb4_general_ci | YES | MUL | NULL | | select,insert,update,references | | | archived_date | datetime(6) | NULL | NO | MUL | NULL | | select,insert,update,references | | | thread_depth | int(11) | NULL | NO | | NULL | | select,insert,update,references | | | thread_order | int(11) | NULL | YES | MUL | NULL | | select,insert,update,references | | | mailinglist_id | int(11) | NULL | NO | MUL | NULL | | select,insert,update,references | | | parent_id | int(11) | NULL | YES | MUL | NULL | | select,insert,update,references | | | sender_id | varchar(255) | utf8mb4_general_ci | NO | MUL | NULL | | select,insert,update,references | | | thread_id | int(11) | NULL | NO | MUL | NULL | | select,insert,update,references | | | sender_name | varchar(255) | utf8mb4_general_ci | YES | | NULL | | select,insert,update,references | | +-----------------+--------------+--------------------+------+-----+---------+----------------+---------------------------------+---------+ 16 rows in set (0.004 sec)
This looks fine, too, doesn't it?
utf8mb4_general_ci is only a collation sequence. It is not the character set of the database.
The bottom line is if you are still getting the subject error it is because the character set of the database and/or the hyperkitty_email table is utf8mb3.
There several threads on this in the archives (search for utf8mb4) and at least one issue at https://gitlab.com/mailman/hyperkitty/-/issues/248 that have information about fixing this.
I don't know for sure about MariaDB, but for MySQL you can also add
[mysqld]
character-set-server=utf8mb4
collation-server=utf8mb4_general_ci
to the MySQL configuration file.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan