Closed Bug 1898274 Opened 1 year ago Closed 8 months ago

Russian letters in imap folder names don't show

Categories

(MailNews Core :: Networking: IMAP, defect)

Thunderbird 115
defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: porton, Unassigned)

References

Details

(Whiteboard: [has protocol log])

Attachments

(2 files)

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36

Steps to reproduce:

I opened my view of folders with a new version of Thinderbird

Actual results:

I see a nonsense on the place where before Russian letters were. See the attached screenshot.

Expected results:

I should see Russian letters.

An imap log might help shed some light on this. See https://wiki.mozilla.org/MailNews:Logging

Component: Untriaged → Folder and Message Lists
Component: Folder and Message Lists → Networking: IMAP
Product: Thunderbird → MailNews Core

Related to bug 1953747?

Flags: needinfo?(gds)
Summary: Russian letters in folder names don't show → Russian letters in imap folder names don't show
Whiteboard: [has protocol log]

Reporter Victor,
Thanks for the log and sorry for long delay in getting back to you.
In the log it shows activity with at least two servers, gmail and yandex. Are you seeing problems only on the yandex account(s)? Are you also seeing problem with gmail account(s)?
I see that yandex does not support the UTF8=ACCEPT imap capability but gmail does. Not sure if that would cause the problem, but it's interesting.
Please check the setting of mail.server.default.allow_utf8_accept pref in config editor. It should be set to default value true. If not, set it true and restart TB and see if that helps.
If doesn't help, please paste into your response to this comment the Cyrillic/Russian character string you expect to see and I'll try to create a folder with that name using an account that does not support imap capability UTF8=ACCEPT.

Flags: needinfo?(gds)

Now my Russian-named folders are shown correctly.

Ok, I'll go ahead and close this as INVALID. But I'll still ask if you know what fixed it, if you know.

Status: UNCONFIRMED → RESOLVED
Closed: 8 months ago
Resolution: --- → INVALID
See Also: → 1953747
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: