On 1/25/21 11:42 PM, David Partain via Mailman-users wrote:
Hi Gordon (and Mark)!
I have the same issue, and have changed the configuration in /etc/mailman3/mailman-web.py to:
DATABASES = { 'default': { 'ENGINE': 'django.db.backends.mysql', 'NAME': 'mailman3web', 'USER': 'mailman3web', 'PASSWORD': 'xxxxxxxxxxxxxxxxxx', 'HOST': 'localhost', 'PORT': '', 'OPTIONS': { 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", 'charset': 'utf8mb4', }, } }
and restarted stuff, but I cannot tell that it has changed anything.
That should do it. I think the original message should have been saved as a queue entry in Mailman's var/archives/hyperkitty/spool/ directory. If this is the case, it would have been retried and produced the same error with each new post, and after you made the above change, it would have been archived and the errors stopped.
Do I need to do something with the database itself (which is somewhat outside my comfort zone...) to make this work?
Are you saying you are still seeing these errors? If so, it may be a different error. What is the exact error message? We don't need all the Django stuff, just the part equivalent to
Internal Server Error: /mailman3/hyperkitty/api/mailman/archive OperationalError at /hyperkitty/api/mailman/archive (1366, "Incorrect string value: '\xF0\x9F\xA4\xA3\xF0\x9F...' for column mailman3web.hyperkitty_email.content at row 1")
from the OP.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan