On 6/15/20 9:43 AM, Gilles Filippini wrote:
Hi,
I'm seeing the above error in mailman-core logs each time an email is processed. Is there something I missed in the configuration? I'm using dockerized mailman 0.3 from maxking.
I'm guessing you have one message in var/archives/hyperkitty/spool/ that is causing this issue. The message itself will probably have invalid utf-8 encodings in a message part declared as charset=utf-8.
Every time a new message is archived, HyperKitty reprocesses this message and hits the error again.
You can examine the message with bin/mailman qfile. It is a Python
pickle of a message object.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan