Path: ...!eternal-september.org!feeder2.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.lang.python
Subject: Re: Printing UTF-8 mail to terminal (Posting On Python-List
 Prohibited)
Date: Thu, 31 Oct 2024 19:35:50 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 14
Message-ID: <vg0m6l$2qq89$2@dont-email.me>
References: <878qu49tii.fsf@zedat.fu-berlin.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 31 Oct 2024 20:35:50 +0100 (CET)
Injection-Info: dont-email.me; posting-host="d4b447124d23a399310d6ccfb3eed0bc";
	logging-data="2976009"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18njh6r27BjE10fFpfUu2ja"
User-Agent: Pan/0.160 (Toresk; )
Cancel-Lock: sha1:keyWe1kzu+W3FQ9TSmNtqCfPGN8=
Bytes: 1557

On Thu, 31 Oct 2024 16:33:41 +0100, Loris Bennett wrote:

>   Dies ist eine =C3=9Cbung.
> 
> What do I need to do to prevent the body from getting mangled?

I don’t think that’s actually getting mangled, that is how the actual 
message body looks. What you have there is called “quoted printable” 
encoding, and it’s a standard way to ensure the message body consists only 
of 7-bit ASCII.

If you look at the source of the message, you should see a header line 
like “Content-Transfer-Encoding: quoted-printable”. This is how your email 
client knows how to display the text properly.