On 9/23/23 02:54, Jana Berger wrote:
I have multiple control messages, all received from my instance which all contain the "Content-Transfer-Encoding: base64" marker, their contents is plain text (Content-Type: text/plain; charset="utf-8"), but they are still encoded using base64.
It seems you are saying these messages are valid. I.e. they specify "Content-Transfer-Encoding: base64" and the body is in fact base64 encoded. This is as they should be.
Of course that is not proof, but an indication that it is either done by the mail server itself or widely across MUAs.
As you say, this suggests that some MTA in the path to your user or the user's MUA is responsible for decoding the base64 encoded body but leaving the "Content-Transfer-Encoding: base64" header as is.
Global "Preferred language" is "English (USA)", which is not overridden by the list in question. I have not changed the default encoding. Is there a surefire way to detect this?
My mailman.cfg has no section pertaining to encoding, and all related files also do not mention encoding.
The Subject: and body of these messages should be ascii, not utf-8 unless you have something like
[language.en]
charset: utf-8
in your mailman.cfg
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan