On 24.09.2023 16:52, Mark Sapiro wrote:
On 9/24/23 07:20, Stephen J. Turnbull wrote:
The only thing I can think of at the moment that might move the discussion forward is if Mark knows how to run his test in your Docker environment to see if it also produces Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit
Assuming there is not something like
[language.en] charset: utf-8in your mailman.cfg overriding the default us-ascii charset for English, if you send a message From: yourself to list-confirm-xxxxxxx@example.com with Subject: Re: Your confirmation is needed to join the list@example.com mailing list (replacing list and example.com with the actual list and domain), you should receive a response like (some headers removed)
Subject: The results of your email commands From: list-bounces@example.com To: mark@example.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-ID: <169556563227.2592.7908020161516725770@example.com> Date: Sun, 24 Sep 2023 07:27:12 -0700 Precedence: bulk X-Mailman-Version: 3.3.9b1 List-Id: A test list <list.example.com> List-Help: <mailto:list-request@example.com?subject=help> List-Owner: <mailto:list-owner@example.com> List-Subscribe: <mailto:list-join@example.com> List-Unsubscribe: <mailto:list-leave@example.com> The results of your email command are provided below. - Original message details: From: Mark Sapiro <mark@example.com> Subject: Re: Your confirmation is needed to join the list.example.com mailing list. Date: Sun, 24 Sep 2023 07:27:10 -0700 Message-ID: <20230924142710.GA23819@example.com> - Results: Confirmation token did not match - Done.What do you get?
Well, that confirms it.
I send the mail from an account at GMX and received the Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64
with a properly (!) base64-encoded message body.
I then send the mail both from my own mail system (which is also the one being used by Mailman) and got
Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8"
with no encoding on the message. Lastly, I send the same mail from a GoogleMail account, which also received
Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8"
with no encoding.
... which means this is almost surely a bug in the MTA of GMX, which will be much, much more difficult and unlikely to be fixed - that is why I had hoped for this to be an issue in/with Mailman ;)
Thank you for the pointers and help!