On Dec 4, 4:44 pm, [EMAIL PROTECTED] (Peter J. Holzer) wrote:

> 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.

Ok, understand. I read RFC 3490 which says that IDN should be
implemented on client side; which is also my opinion. On the over
hand, IDN support has not been build in into many mail clients for
years now. The only mail app that supports IDN that I know is Apple
Mail in the newest version that comes with OS X 10.5. That why I
thought that its time to do something and do it the most simple and
flexible way - like the philosophy of qpsmtpd - and implement it into
the server side. This way almost any mail client is supported from one
second to another.

> 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?

I tested it with swaks.pl (http://www.jetmore.org/john/code/#swaks)
and it sends the "mail from" and "rcpt to" unmodified over the line. I
improved my IDN plug-in a bit and it works quite well right now in my
environment. Nevertheless, two patches need to be applied to lib/
Qpsmtpd/Address.pm in order to handle subdomain parts that contain non
7bit ASCII and to allow overwriting of $self->{_host}. Those patches
will never be part of the official qpsmtpd for sure, but for anyone
who wants IDN support it's easy to do it.

Regards, Marc

Reply via email to