Account character encoding settings ignored on new Usenet post composition

RESOLVED INVALID

Status

Thunderbird
Message Compose Window
RESOLVED INVALID
4 years ago
4 years ago

People

(Reporter: frederic, Unassigned)

Tracking

31 Branch
x86
All

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:33.0) Gecko/20100101 Firefox/33.0
Build ID: 20141027150301

Steps to reproduce:

My ISP makes its supports with some Usenet hierachies, but they are not configured to accept UTF8 encoding (welcome to the XXI-st century ;-)), hence I configured my Usenet account to use "Western (Euro) (ISO-8859-15)" as the Default Character Encoding in Server Settings. Until my upgrade to Thunderbird 31.2 (I don't remember from which version I upgraded), this settings was honoured despite the fact the Preferences > Display > Formatting > Advanced was defining the default character encodings for sending and receiving mail as Unicode.


Actual results:

Now, when I wrote new messages to post on one of those groups, the message encoding is set to Unicode instead of Western, meaning I must change it manualy in Options > Character Encoding before posting the message or it is refused by the server due to the UTF8 encoding.
(I'm using MacOSX version of Thunderbird, but according to complaints on the groups, Windows and Linux users are also concerned by that problem.)


Expected results:

Like with the previous versions: when opening the new message composition window, the message's character encoding should be the character encoding defined in the account's default settings and not the Outgoing mail's default character encodings for sending and receiving mail defined in Preferences > Display > Formatting > Advanced, as the Usenet server settings are more specific, and Usenet posts are not mails ;-)
(Reporter)

Comment 1

4 years ago
More diriged steps to reproduce the problem:
- Add a new newsgroup account (or reuse one ;-)) in your profile of a Thunderbird 31.2,
- subscribe to a *.test hierarchy,
- set the Default Character Encoding in its Server Settings (let's say one of the Western encoding familly) to something different from Preferences > Display > Formatting > Advanced > Character Encodings > Outgoing Mail (which should be Unicode by default),
- open the composition window for a new post in the selected *.test hierarchy, write some test text (ASCII only characters so there can't be any conversion problem involved with characters that can only be rendered with the Unicode encoding), and have a look at Options > Characters Encoding to see it is set to Unicode instead of Western,
- post your message, refresh the *.test group and open the source of your test message to verify that the "Content-Type:" charset value has also been set to Unicode instead of the expected Western.
(Reporter)

Comment 2

4 years ago
(Didn't find the right component at redaction time; missed the platform field)
Component: Untriaged → Message Compose Window
OS: Mac OS X → All
(In reply to frederic from comment #0)
> Steps to reproduce:
> My ISP makes its supports with some Usenet hierachies, 
> but they are not configured to accept UTF8 encoding (welcome to the XXI-st century ;-)),
> hence I configured my Usenet account to use "Western (Euro) (ISO-8859-15)"
> as the Default Character Encoding in Server Settings.

IIUC, the "Default Character Encoding in Server Settings" is never for "default of character set in mail composition".
It's for "fall back character encoding in mail display" when "charset of mail in folder of this account" is not set.
So, the "Default Character Encoding in Server Settings" is currently used as "default of Folder Properties/General, Fall back Character Encoding" when folder is created/renamed or newsgroup is subscribed.

I believe "Default charset in mail/news post composition" is still "Preferences > Display > Formatting > Advanced > Character Encodings > Outgoing Mail" in Thunderbird.

> and Usenet posts are not mails ;-)

prefs.js setting corresponds to "Preferences > Display > Formatting > Advanced > Character Encodings > Outgoing Mail" in Thunderbird is following,
     mailnews.send_default_charset
even though .string of "Character Encoding/Outgoing *MAIL*" is set in UI panel of Tb.

prefs.js setting corresponds to "Default Character Encoding in Server Settings for a news server" in Thunderbird is following,
    mail.server.server#.charset
even if *MAIL*.server.server#.type = nntp is used for News Server setting in Tb.
FYI.
prefs.js setting corresponds to "Preferences > Display > Formatting > Advanced > Character Encodings > Incomming Mail" in Thunderbird is following.
     mailnews.view_default_charset
IIUC, "fall back character encoding in Viewing mail, in Auto-Detect of charset etc." is this mailnews.view_default_charset.
Per folder "Folder Properties/General, Fall back Character Encoding" setting, which initially comes from  mail.server.server#.charset, is used only when "Apply encoding to all messages in this folder" is checked.
(Reporter)

Comment 5

4 years ago
(In reply to WADA from comment #3)
> I believe "Default charset in mail/news post composition" is still
> "Preferences > Display > Formatting > Advanced > Character Encodings >
> Outgoing Mail" in Thunderbird.

 Thx WADA, you're right, I was wrong; I reinstalled a few (randomly chosen) previous version to check their behaviour, and they all use the encoding set in the "Outgoing Mail" parameter (prefs.js' mailnews.send_default_charset value). I should have take the time to do this before opening this bug report.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.