On 12/8/20 9:05 AM, matthew@alberti.us wrote:
From what I've been reading, it seems like Mailman3 expectsthe mysql database to use UTF8 encoding. It appears, by default, that when using the docker-mailman containers, that the character set is set to latin1. This may explain why there are lots of import errors, and maybe also why there are a lot of errors when threads are deleted in hyperkitty's UI.
Is it the case that UTF8 is the preferred character set? Ialso saw some threads indicating that maybe utf8mb4 is more preferred. I'd like to try to change the character_set on the database, if that is advisable.
You want the MySQL encoding for the Mailman database to be utf8mb4. If not, as Ruth says, you will have issues with 4-bute utf-8 encodings. See <https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_project...>
Also, is Hyperkitty 1.3.4 officially released? I see that thelist.org instance is using it, but the latest announce I've seen is for 1.3.3.
No, it is not. lists.mailman3.org and mail.python.org both run the HEADs of the GitLab branches so they are generally ahead of the latest releases.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan