On Tue, 2022-03-08 at 16:07 +0100, Milan Crha via evolution-list wrote: > On Tue, 2022-03-08 at 15:45 +0100, Sorin Srbu via evolution-list wrote: > > I use EWS > > Hi, > I see, that's okay. I tried with evolution-ews (and the Office365.com > server) and I cannot reproduce it here. The message is received > properly here, with ISO-8859-1 and quoted-printable content transfer > encoding, just as Evolution sends it to the server and the same as your > message to the mailing list has set. > > I thought there's some problem on the evolution-ews side, breaking the > message when passing the message content into the server, but it's not > the case. > > Change your encoding to the UTF-8 (possibly to workaround the others' > end bug). > Bye, > Milan
According to various sources from Google I searched yesterday, some say Office365 does occasionally do some unnecessary conversions that may break the text encoding if a 3rd party mail client is used. Be that as it may, I'll take your advice and run with Unicode UTF-8 for a while and see what the recipients at work have to say. Will report back in a while with results. Thanks all for now! -- Sorin Srbu, Serverdrift Tele: 08-524 84166 Karolinska Institutet Universitetsbibliotek Avdelningen för Verksamhetsstöd Enheten för Teknikstöd och Bildproduktion # They say you can't buy happiness, but you can buy a # motorcycle, and that's pretty damn close!
signature.asc
Description: This is a digitally signed message part
_______________________________________________ evolution-list mailing list [email protected] To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
