Just a note that there can be database complications when updating from mailman 2 to mailman 3. If the new list server (Ubuntu 22) has done this upgrade, which is likely, it would be safest for people to update their list archives before the downtime, in case there are unexpected migration issues. ---------- Forwarded message ---------- From: Odhiambo Washington <odhiambo@gmail.com> Date: Tue, 20 Dec 2022 09:50:21 +0300 Subject: [MM3-users] Re: Errors while importing mm2 list archives To: mailman-users@mailman3.org On Tue, Dec 20, 2022 at 3:52 AM Mark Sapiro <mark@msapiro.net> wrote:

On 12/17/22 23:22, Odhiambo Washington wrote:

...

I have dropped the DB, recreated, ...

When you created the DB did you specify `CHARACTER SET utf8mb4`, e.g.

CREATE DATABASE mailmansuite CHARACTER SET utf8mb4

Yes. That is what I do at the minimum for my databases unless specific instructions exist against it. So it seems like I have done everything that is commonly expected, but the import still fails on several messages. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) _______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/... This message sent to 0xloem@gmail.com