On 9/22/23 09:32, Stephen J. Turnbull wrote:
To diagnose, we really need to see that in context of the raw message as received by the user.
It was posted. The issue is the message declares
Content-Transfer-Encoding: base64
but the body is not base64 encoded so the MUA tries to base64 decode it and even though that's invalid, produces the garbled output.
The only other thing I can think of is it might have something to do with your internationalization settings. What is the default language of the list? (This is available in Postorius.) Have you changed the default encoding for English on your site? (I think you need to look in mailman.cfg for this.) What is the default language of the site?
I note that the message also declares
Content-Type: text/plain; charset="utf-8"
and Python's email package will base64 encode utf-8 message bodies. I also note that the messages Subject: is RFC 2047 encoded as utf-8. These tell me that the user's preferred_language if set or the list's preferred_language is not English or the charset for English is changed to utf-8.
I tried to duplicate this in a test installation with the charset for English set to utf-8, but I get a similar response but with
Subject: =?utf-8?q?The_results_of_your_email_commands?=
and
Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan