Character encoding wrong in the email address when using non-ascii in domain part of email address (IDN)
Categories
(Thunderbird :: Account Manager, defect, P3)
Tracking
(Not tracked)
People
(Reporter: marcinzetx, Unassigned)
References
Details
(Keywords: intl)
Attachments
(1 file)
|
25.74 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.163 Safari/537.36
Steps to reproduce:
The problem occurs when entering Polish characters in the account configuration exactly the email address.
For example, I enter the email address:
marcin@łyżka.pl
Actual results:
I approve the changes and leave the account configuration.
Then I enter the account configuration again, the e-mail address shows the address:
marcin@By|ka.pl
When I send emails, the recipient sees the address: marcin@By|ka.pl
instead: marcin@łyżka.pl
so he can't reply to the message
Expected results:
After confirming the changes in the account configuration, the e-mail address should be as follows: marcin@łyżka.pl
Comment 1•6 years ago
|
||
Sounds like a bug, but not a security bug? If it remains hidden as a security bug very few people will see it.
Comment 3•6 years ago
|
||
'ł' (small L with stroke) is U-0142 and 'ż' (small Z with dot above) is U-017C
'B' is 0x42 and '|' is 0x7C
Looks like the input is in Unicode and then it's being converted to ASCII (or maybe Latin-1) by just dropping the first byte. We had some ancient JavaScript<-->C apis that did that and maybe those are still being used here? If we have to store it single-byte then we should convert it to UTF8 instead.
I was unable to deselect the security option: Only users in all of the selected groups can view this bug.
So I created a new bug so that it would be available to everyone.
https://bugzilla.mozilla.org/show_bug.cgi?id=1630718
Updated•6 years ago
|
Comment 5•6 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)
Is there anything known about when the character encoding bug is fixed?
Comment 7•6 years ago
|
||
We don't really support IDN mails too well atm.
For the actual issue, which is just one small part of the support, fields like email should be AUTF8String instead of ACString - https://searchfox.org/comm-central/rev/9f453dd597f0b985b8fe7689b239e3b70de7749d/mailnews/base/public/nsIMsgIdentity.idl#41
Updated•6 years ago
|
Updated•1 year ago
|
Updated•1 month ago
|
Description
•