Closed Bug 961908 Opened 11 years ago Closed 9 months ago

Accounts with IDN in server names work poorly

Categories

(MailNews Core :: Account Manager, defect)

defect

Tracking

(thunderbird_esr115 wontfix)

RESOLVED FIXED
123 Branch
Tracking Status
thunderbird_esr115 --- wontfix

People

(Reporter: jcranmer, Unassigned)

References

Details

(Whiteboard: [fixed by bug 1870720])

I've been trying to set up an IDN/EAI testbed for Thunderbird development, and after several failed attempts to set up an account to my client, I found what appears to be a major IDN issue. Given that I didn't trust the account dialog to accept U-labels, I tried the A-label, which for my server is xn--bckc7bj7f1a6vd.tlalocan. (Try having to retype that several times). This passes all the initial validations, and when we finally hit the VerifyLogin stage, it all of a sudden blows up. When we're in nsMsgDBFolder::ParseURL, we have: (gdb) p mURI $1 = {<nsACString_internal> = {mData = 0x7f8db5649108 "imap://jcranmer@mail.xn--bckc7bj7f1a6vd.tlalocan", mLength = 48, mFlags = 5}, <No data fields>} However, when we get to nsMsgAccountManager::FindServerByURI, we get: (gdb) p hostname.get() $5 = (const nsACString_internal::char_type *) 0x7fff35c072a0 "mail.ケツァルコアトル.tlalocan" So nsStandardURL helpfully standardized the IDN for us (server->GetHostName() has the xn-- variant still), and we wind up being unable to match the URL anymore, causing the entire process to crash and burn.
See Also: → 811272
Severity: normal → S3

I fixed this in bug 1870720 (and dependents).

Status: NEW → RESOLVED
Closed: 9 months ago
Resolution: --- → FIXED
Whiteboard: [fixed by bug 1870720]
Target Milestone: --- → 123 Branch
Depends on: 1870720
You need to log in before you can comment on or make changes to this bug.