Closed Bug 605069 Opened 14 years ago Closed 14 years ago

ICANN's IDNs not showing properly in Thunderbird

Categories

(Thunderbird :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 127399
Thunderbird 11.0

People

(Reporter: Milos, Unassigned)

Details

As you already might know, ICANN is experimenting with localized top-level domains, and as of 5th May 2010, there are 3 new localized TLDs:

http://icann.org/en/announcements/announcement-05may10-en.htm

Sending and receiving emails from email addresses that are on top of such domain names works ok in Thunderbird, except that domain names are not shown in native language and script, but instead represented like "address@xn--e1afmkfd.xn--80akhbyknj4f".

However, while sending emails to such addresses works with mailto links, pasting such an address in To: field and clicking send produces following error:

"An error occurred while sending mail. The mail server responded:  syntax error (#5.5.4). Please check the message recipient mailtest@مثال.إختبار and try again."
So this sounds like https://bugzilla.mozilla.org/show_bug.cgi?id=238016


>"An error occurred while sending mail. The mail server responded:  syntax error
(#5.5.4). Please check the message recipient mailtest@مثال.إختبار and try
again."

Is the smtp error, meaning that your smtp server might not be IDN compatible. Can you investigate with your ISP ?
I'm not sure if I know how to test it besides trying it via webmail. I tried horde and roundcube, none of which support IDN. But I found a bug which this may be duplicate of:

https://bugzilla.mozilla.org/show_bug.cgi?id=127399

It is pretty old, but it probably has more info.
(In reply to comment #2)
> I'm not sure if I know how to test it besides trying it via webmail. I tried
> horde and roundcube, none of which support IDN. But I found a bug which this
> may be duplicate of:
> 
> https://bugzilla.mozilla.org/show_bug.cgi?id=127399
> 
> It is pretty old, but it probably has more info.

Let's dup as until these are resolved, we won't be able to test anyway.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.