It didn't work in Mozilla 1.4.b or 1.01 either. I think I read something about an add-in or module somewhere in the docs for 1.5, but you have to hunt for it and choose to include it.

I don't read or speak any languages that use IDN characters, so I would not choose to implement additional modules and prefer to not receive email in languages I don't understand. I think many people will feel the same way, so the market for the IDN domains will be within the areas where the languages are spoken/read. I don't know how ISPs will handle email, however. Many filter on non-english character sets because of the high numbers of spam using them. It's going to be interesting.

Interestingly, some of the filters used for UCE require domain name matches to IP's and valid domain names. I'm not familiar enough with all the filters or whether IDNs would pass the tests now in use.

The example I posted was a subject line, which would automatically trigger a spam filter.

"I myself own an IDN domain name which corresponds to my last name, which contain scandinavian characters outside A-Z. Yet I'm perfectly capable of writing in English to those who don't understand scandinavian languages."

If that is the case, why not use your english-based domain name to write to those who speak English and use the IDN where people speak another language?

I guess my point is that if I don't understand scandavian, my filters would block it in headers and content. I see no reason to accept mail that I could not understand. If I did not understand English, I would most likely block it for the same reason unless I wanted to hire a translator.:)

I recently received email from an administrator of a Romanian (I think) server to whom I had sent notice of suspcious activity. Since I could not read the email, it was deleted. Since it was that server that was attacking me, I blocked it after checking the header to make sure the IP was the same. There is no sense in trying to communicate when I can't understand the communication, right?