Yahoo, fixed! For anyone interested: When sending a message with content-type multipart/alternative, the charset must of be specified for each part separately, otherwise MIMEDocument will encode them incorrectly, and in turn, the recipient (here: mailman/pipermail (?)) will convert the unknown characters such as ümläutß, âccénts, and even tabs into Character value: 16rfffd (Unicode replacement character) � for the representation in the monthly archive files (even though the single HTML files look well). :-)

On 2022-11-28T13:55:06+01:00, christoph.thiede at student.hpi.uni-potsdam.de wrote:

> This is another test. Sorry ...
> 
> Sent from SIT (3).
> 
> Ümläutß, sorry for the noisé!
> Tab	tab	tab	
> 
> RxMatcher>>matchAgainstLookbehind:positive:nextLink: {matching} · ct 3/6/2020 20:09 (changed)
> 
> Best,
> Christoph
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20221128/a160236e/attachment.html>
> 
>