Thank you, Mark. I see this in mailman.log. I had looked there for her email address, but it does not appear, so I moved on to the smtp.log.
In
Jun 26 17:18:11 2023 (1243315) ACCEPT: ^M <CH3PR12MB82593801A1DF2E329E977046BE27A@CH3PR12MB8259.namprd12.prod.outlook.com> Jun 26 17:18:11 2023 (1243319) Uncaught runner exception: unknown encoding: iso-8859-8-i Jun 26 17:18:11 2023 (1243319) Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.9/site-packages/mailman/core/runner.py", line 179, in _one_iteration self._process_one_file(msg, msgdata) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/mailman/core/runner.py", line 272, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/mailman/core/pipelines.py", line 53, in process handler.process(mlist, msg, msgdata) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/mailman/handlers/mime_delete.py", line 382, in process process(mlist, msg, msgdata) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/mailman/handlers/mime_delete.py", line 151, in process reset_payload(msg, firstalt) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/mailman/handlers/mime_delete.py", line 202, in reset_payload msg.set_payload(subpart.get_payload(decode=True).decode( LookupError: unknown encoding: iso-8859-8-i Jun 26 17:18:11 2023 (1243319) SHUNTING: 1687825091.8457294+478565324778f2eb6f0fecaeccbd29596edaef53
I also see this in queue/shunt:
mailman@list:~/var/queue/shunt$ ls -ltr total 88 -rw-rw---- 1 mailman mailman 7168 Feb 17 23:03 1676703781.903885+fdcba88c680f50a0799c672cd0abe82e4bfe19b3.pck -rw-rw---- 1 mailman mailman 19821 Apr 2 07:08 1680444501.0831451+e110b8c5c20ba3f87c1cea1c5f38e74a6cf8f1c5.pck -rw-rw---- 1 mailman mailman 19489 Jun 18 11:52 1687114364.41209+1684717da96ff76d1ce773a0cf39c5f8b63e9078.pck -rw-rw---- 1 mailman mailman 20274 Jun 18 19:01 1687140067.64057+7f77c1ebca490831f58ef9cfde06109081a4e7d6.pck -rw-rw---- 1 mailman mailman 20085 Jun 26 17:18 1687825091.8457294+478565324778f2eb6f0fecaeccbd29596edaef53.pck
The three last entries coincide with the captured messages.
Finally, in the captured message source (the last which was Cc'd to me) I do see this:
Content-Type: text/plain; charset="iso-8859-8-i"
Which matches the complaint in the mailman log.
In the message that did get accepted, I see this:
Content-Type: text/plain; charset="utf-8"
Another difference: The posted message shows Content-Transfer-Encoding: base64 The shunted message shows Content-Transfer-Encoding: quoted-printable
It appears that the two messages are, indeed, different, despite the similar looks when rendered.
My question thus changes to:
a. Should she be doing something special when sending to the lists?
b. If not, is my setup in need of change?Yours,
AllanOn 6/26/23, 20:44, "Mark Sapiro" <mark@msapiro.net <mailto:mark@msapiro.net>> wrote:
On 6/26/23 8:09 PM, Allan Hansen wrote:
Hi all,
One of my subscribers is trying to send a message to a list, but it is not being posted. The smtp.log shows that her first message was posted, but a second message (with 2 retries) was not:
mailman@list:~/logs$ grep herName smtp.log Jun 18 11:22:05 2023 (1243316) ('127.0.0.1', 56686) >> b'MAIL FROM:<herName@hotmail.com <mailto:herName@hotmail.com>> SIZE=40109' Jun 18 11:22:05 2023 (1243316) ('127.0.0.1', 56686) sender: herName@hotmail.com <mailto:herName@hotmail.com> Jun 18 11:25:01 2023 (1243318) <CH3PR12MB82593510B90D8F05177C606BBE5EA@CH3PR12MB8259.namprd12.prod.outlook.com <mailto:CH3PR12MB82593510B90D8F05177C606BBE5EA@CH3PR12MB8259.namprd12.prod.outlook.com>> post to theList@domain.tlc <mailto:theList@domain.tlc> from herName@hotmail.com <mailto:herName@hotmail.com>, 40061 bytes Jun 18 11:52:42 2023 (1243316) ('127.0.0.1', 48448) >> b'MAIL FROM:<herName@hotmail.com <mailto:herName@hotmail.com>> SIZE=18343' Jun 18 11:52:42 2023 (1243316) ('127.0.0.1', 48448) sender: herName@hotmail.com <mailto:herName@hotmail.com> Jun 18 19:01:04 2023 (1243316) ('127.0.0.1', 59550) >> b'MAIL FROM:<herName@hotmail.com <mailto:herName@hotmail.com>> SIZE=19123' Jun 18 19:01:04 2023 (1243316) ('127.0.0.1', 59550) sender: herName@hotmail.com <mailto:herName@hotmail.com> Jun 26 17:18:11 2023 (1243316) ('127.0.0.1', 44732) >> b'MAIL FROM:<herName@hotmail.com <mailto:herName@hotmail.com>> SIZE=18930' Jun 26 17:18:11 2023 (1243316) ('127.0.0.1', 44732) sender: herName@hotmail.com <mailto:herName@hotmail.com>
At the second retry she copied me and I saw nothing untowards in her message. She's not getting any error return messages and her subscription is OK. Both messages were multipart/alternative and both contained Hebrew text.
I told her I'd look at this, but I'm at a loss.
smtp.log is not very useful for diagnosing things like this. It only says a message was received, not why it didn't result in a post from the list as in the first case. What's in mailman.log with those timestamps?
-- Mark Sapiro <mark@msapiro.net <mailto:mark@msapiro.net>> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list -- mailman-users@mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave@mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org <mailto:mailman-users@mailman3.org>/message/F4K7HYUYSWEKF6LT35UCT3KBJX6GHY4I/
This message sent to hansen@rc.org <mailto:hansen@rc.org>