When mail is received from an Internationalized Domain Name, it is displayed in the message view as Punycode. This affects both the recipient and source addresses. I'm not sure why claws-mail is linked against libidn if it's not going to get used. I would expect to see translated UTF-8 characters there instead of ASCII, even though of course only 7-bit is allowed in the original email.
If a message must be only 7-bit, it can't display those characters. Or did I misunderstand something?
(In reply to comment #1) > If a message must be only 7-bit, it can't display those characters. To be more syntactically correct, it can't contain those characters.
Let me explain better: Let's say my domain is xn--lfa.org (ĺ.org - not a real domain). When I type "xn--lfa.org" into my browser's address bar, it does a DNS lookup for "xn--lfa.org", and that is the web site it goes to -- but it will display an l with an acute accent. The purpose of the punycode is only to provide compatibility with applications that only support ASCII. So, the analogy is like this: Claws will receive an email that contains only ASCII characters. To the user, however, it will render them as international characters. This is the only way non-English languages could be supported without having to upgrade every mail server on the internet. When I get an email from "foo@xn--lfa.org", I expect to see "foo@ĺ.org" in the "from" field. When I try to send an email to "bar@ĺ.org", I expect claws-mail to greet the postfix server with "RCPT TO: <bar@xn--lfa.org>". Currently, the message view shows punycode and sending an email with an IDN recipient results in an SMTP error.
By the way, I think the behavior I'm describing is standard - for instance, if I view the EXACT SAME message through the Zimbra web interface, I see international characters. And apparently this bugzilla also doesn't do UTF-8 because it represented my "l with acute accent" as "ĺ". Just imagine the character there :-P.
can you attach an example email?
(In reply to comment #5) > can you attach an example email? > Example as requested (this should display an enya in both sender and recipient): Date: Thu, 10 Jul 2008 14:14:33 -0500 From: Somebody <foo@xn--ida.org> To: Somebody Else <bar@xn--ida.org> Subject: IDN test Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This email has an IDN sender and recipient.
By the way, Firefox only displays IDNs for certain (hardcoded) TLDs. This is to prevent fraud (paypal.com using a cyrillic 'a' is the classic example). But since email is unauthenticated anyhow, I don't think there's a concern here. If the message is signed the signature will show up as punycode. No worries.
*** Bug 1846 has been marked as a duplicate of this bug. ***
*** Bug 2287 has been marked as a duplicate of this bug. ***
*** Bug 3257 has been marked as a duplicate of this bug. ***
*** Bug 3519 has been marked as a duplicate of this bug. ***
*** Bug 4555 has been marked as a duplicate of this bug. ***
*** Bug 4646 has been marked as a duplicate of this bug. ***
Is it intended to change that? The display of the addresses is one thing, the non-working links another.
They are 2 sides of the same coin.