On 1/2/22 11:00 AM, Seth Seeger wrote:
I have a case where a user (set to be moderated), posts a message. She got the appropriate email back saying she was being held for moderation. However, the moderator did not get the email. I found the following block in mailman.log:
Dec 28 19:37:44 2021 (33) Uncaught runner exception: 'ascii' codec can't encode character '\u2019' in position 5: ordinal not in range(128) Dec 28 19:37:44 2021 (33) Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3.8/site-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3.8/site-packages/mailman/runners/incoming.py", line 79, in _dispose process(mlist, msg, msgdata, start_chain) File "/usr/lib/python3.8/site-packages/mailman/core/chains.py", line 79, in process link.function(mlist, msg, msgdata) File "/usr/lib/python3.8/site-packages/mailman/chains/hold.py", line 234, in _process text = MIMEText(expand(template, mlist, substitutions), File "/usr/lib/python3.8/email/mime/text.py", line 42, in __init__ self.set_payload(_text, _charset) File "/usr/lib/python3.8/email/message.py", line 315, in set_payload payload = payload.encode(charset.output_charset) UnicodeEncodeError: 'ascii' codec can't encode character '\u2019' in position 5: ordinal not in range(128) Dec 28 19:37:44 2021 (33) SHUNTING: 1640720264.0541506+b139f885caa9444586b43093a09991b7c19581e6
There are two owners listed, one of them is also listed as the moderator.
This is redundant. Having the same user as both owner and moderator only results in possible duplicate notifications. There is no reason to have an owner also be a moderator.
"mailman version" says: GNU Mailman 3.3.4 (Tom Sawyer) We are running from Docker. I can send you the pck file offline if that would help.
Please do send me the shunted .pck. what is going on is this is an
English language list which has character set ascii and the notice for
some reason has non-ascii, possbbly the Subject: or the user's display
name has non-ascii. But possibly the message itself is defective.
In any case, I'd like to get the shunted message to see if there's something we should fix.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan