On 4/27/23 1:23 PM, bob B via Mailman-users wrote:
Had a message get shunted in /opt/mailman/core/var/queue/shunt/. *** but that is the location in the docker environment, which we are running.
The mailman log shows:
Apr 26 13:09:56 2023 (31) ACCEPT: 2e0e82a5-0924-1777-bed8-34862417fe7e@[Redacted] Apr 26 13:09:56 2023 (35) Uncaught runner exception: 'ascii' codec can't encode characters in position 1198-1200: ordinal not in range(128) Apr 26 13:09:56 2023 (35) Traceback (most recent call last): Apr 26 13:09:56 2023 (35) SHUNTING: 1682514596.7976818+6067e5ddeb70e4aad97977071b5ed00c41999057 Apr 26 13:10:14 2023 (31) ACCEPT: 367fa8b7-97ac-58b3-fb99-458dbb951f5d@[Redacted] Apr 26 13:10:14 2023 (31) ACCEPT: 367fa8b7-97ac-58b3-fb99-458dbb951f5d@[Redacted] Apr 26 13:10:16 2023 (35) Uncaught runner exception: 'ascii' codec can't encode characters in position 1198-1200: ordinal not in range(128) Apr 26 13:10:16 2023 (35) Traceback (most recent call last): Apr 26 13:10:16 2023 (35) SHUNTING: 1682514616.5346222+7292ba8b651bc1bd76a9098733a39090e092add2
Is there anyway to get more info, Is there a more detailed traceback somewhere?
I have never seen anything like this. There should be a complete
Traceback in between the Traceback (most recent call last): line and
the SHUNTING: ... line.
However, I'm pretty sure the issue is a defective email which has non-ascii bytes in an explicit or implicit ascii part.
You can see the raw message by pointing mailman qfile at the shunted
.pck file(s)
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan