GNOME Bugzilla – Bug 486018
Implement IDNA (Internationalized Domain Names in Applications, RFC3490)
Last modified: 2015-02-15 16:30:18 UTC
With this translation it is possible to have non-ascii characters in domain names, without changing anything in the DNS and MTA servers in use today. The application itself should translate a domain containing non-ascii characters into its ascii representation using the algorithm referenced in RFC3490.
+1 on this. IDN domains are becoming more and more popular, Evolution really needs to support this.
Related: http://www.gnu.org/software/libidn/ Not yet a blessed external dependency for GNOME.
*** Bug 571376 has been marked as a duplicate of this bug. ***
Adding 'smtp' tag for the duplicate bug.
+1 on this
*** Bug 593400 has been marked as a duplicate of this bug. ***
*** Bug 505198 has been marked as a duplicate of this bug. ***
+1 on this. Why is the status UNCONFIRMED? I can confirm that this is a problem on Ubuntu 10.04 and Evolution 2.28.3. I have an IDN domain and need to instruct my clients to punycode the domain name before sending emails. According to Wikipedia, IDN domains were introduced in 2004 and reported here in 2007. I think it is time to support it.
UNCONFIRMED versus NEW is meaningless to developers.
who to contact to get this on the feature list of the developer?
JFYI: Version 3.12.2 still does not support IDN domains.
Created attachment 284492 [details] [review] proposed eds patch for evolution-data-server; This should made it work for the mail part. According to my tests, anything using libsoup is safe, because it converts the URL on its own (which means the calendar and book backends are fine). I'm not able to test this thoroughly, I do not have any IDNA domain with a mail account, thus I'll appreciate any real-life testing first. If it'll work, then I can commit this to both the development and the stable version, because the code uses ICU, on which EDS (3.12+) already depends.
(In reply to comment #12) > I'm not able to test this thoroughly, I do not have any IDNA domain with a mail > account, thus I'll appreciate any real-life testing first. If it'll work, then > I can commit this to both the development and the stable version, because the > code uses ICU, on which EDS (3.12+) already depends. There are echo services running at: mailto:testmail@háčkyčárky.cz?subject=IDN or mailto:echo@köthe.de Cheers, Ondřej
Right, I noticed the services, but I expected that the SMTP server will transform the domain name on its own. I did try and it's not the case. The above patch tries to address only the mail accounts on such servers. I'll extend the patch.
I made few more changes and I was able to send a message to both addresses, though I've got a response only from koethe.net (I suppose I failed with some syntax with hackcarky.cz). Thus I make this part of sources right away: Created commit b068eb4 in eds master (3.13.6+) [1] Created commit 3f484c1 in eds evolution-data-server-3-12 (3.12.6+) [1] https://git.gnome.org/browse/evolution-data-server/commit/?id=b068eb4
> I suppose I failed with some syntax with hackcarky.cz You need to have "IDN" in the subject and there's a rate limiting to 1 message per day, so we don't generate backscatter email.
I did have the IDN as subject, but still no reply (it took the koethe server around an hour to reply, while I sent a message to hackycarky before that).
*** Bug 681616 has been marked as a duplicate of this bug. ***