Mark Sapiro writes:
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.
:-(
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?=
I think that's unfortunate. Not really a bug, but the RFCs recommend using the defaults (ie, US-ASCII) where that's possible. I wonder if it's possible to use email.policy to change that.[1]
With respect to the actual problem, I don't have anything to say until we have more information about the relevant settings.
Oh, I guess I also wonder if maybe the language doesn't have a translation for that message yet?
Steve
Footnotes: [1] Speaking of bugs, my MUA decoded that MIME word when it quoted the message even though it's not in the header! Aaargh.