On 2007-12-04 05:32:41 -0800, [EMAIL PROTECTED] wrote: > I run one of the famous new IDN domains - those domains that contains > evil utf-8 characters, like german umlaute or japanese chars. IDN is > around for some years now and more of less supported in all browsers > at least for HTTP. > > I was wondering if someone knows the status of IDN support for SMTP?
As far as I can tell, this is not an issue for SMTP. The MUA is supposed to convert the domain name into ACE format (just like the browser is supposed to convert the domain name before sending an HTTP request). So MTAs always only deal with "ordinary" domain names and never need to know that the domain is "really" an IDN. > Are there plans to add this into common smtpd's like sendmail, qmail, > postfix, exim, etc? Or is this already implemented and I am just not > aware of it? There is no need to implement anything at this level. (I would have preferred to solve the problem at this level rather than having yet another ugly encoding, but IDNs are here and won't change) > Nevertheless, I wrote a IDN plug-in for qpsmtpd: > > http://wiki.qpsmtpd.org/plugins:other:idn > > It's not heavily been tested yet and marked as alpha release. Please > feel free to play around with it and contribute your code/patches. > > Here is what it does: > > This plugin checks if the domain part of a sender or recipient > contains utf-8 chars and converts it into ACE using Puyncode. This may be useful in an MSA for MUAs which don't deal correctly with IDNs. However, such a client probably has other problems with IDNs, too, so I'm not sure if this enough enable them to use IDNs. Which MUAs did you test this with? hp -- _ | Peter J. Holzer | It took a genius to create [TeX], |_|_) | Sysadmin WSR | and it takes a genius to maintain it. | | | [EMAIL PROTECTED] | That's not engineering, that's art. __/ | http://www.hjp.at/ | -- David Kastrup in comp.text.tex
signature.asc
Description: Digital signature
