Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Encoding works for message subject but not for message text

more options

Hi, I'm using ubuntu 14.04 32-bit (german setup). I installed from scratch: Thunderbird 52.6.0 32-bit

I changed some settings in TB, but none related to encoding, thus using UTF-8.

I encounter the following problem sending an email that contains german special letters (e.g äöü): The message subject e.g. "test äöü" is transmitted correctly, but the message body "test äöü" arrives at the receiver as "test ???". This can be tested by myself by including my address CC.

Hi, I'm using ubuntu 14.04 32-bit (german setup). I installed from scratch: Thunderbird 52.6.0 32-bit I changed some settings in TB, but none related to encoding, thus using UTF-8. I encounter the following problem sending an email that contains german special letters (e.g äöü): The message subject e.g. "test äöü" is transmitted correctly, but the message body "test äöü" arrives at the receiver as "test ???". This can be tested by myself by including my address CC.

Chosen solution

Matt, maybe your were right. Now it's working as it should (using "sans-serif"). Perhaps a reboot of the system (or some other change ?) did it. Thanks for your contributions.

Read this answer in context 👍 0

All Replies (5)

more options

What are your Fonts settings? Please post a screenshot of your Fonts & Encodings window.

more options

Hi, please find attached the requested screenshot.

more options

Arial is not a unicode font. Change it to a font that is, or download a unicode version names Arial unicode MS and use that instead.

more options

Sorry, but Wikipedia thinks Arial is a unicode font, please see https://en.wikipedia.org/wiki/Unicode_font#List_of_Unicode_fonts

Be that as it may. The problem persists even if I use "sans serif" which is the installation default font.

more options

Chosen Solution

Matt, maybe your were right. Now it's working as it should (using "sans-serif"). Perhaps a reboot of the system (or some other change ?) did it. Thanks for your contributions.