[EMAIL PROTECTED] escribió:
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 agree: It isn't the servers work to do the transformation, but by
doing so, maybe it can mitigate the problems for the users that simply
"want the mail to get to mydömaín.com" and don't understand about MSAs
MUAs, MTAs, MDAs, etc.
I've done a couple of tests (with a qmail server) to try to see what the
clients are doing:
Outook 2003 seems to just be passing the "to" string to the server, so
it looks like it would help to do the transformation on the server.
Outlook 2003 sends the message and the server bounces it with:
>Hi. This is the qmail-send program at xxxxx.xxx.xxx.
>I'm afraid I wasn't able to deliver your message to the following
>addresses.
>This is a permanent error; I've given up. Sorry it didn't work out.
>
><[EMAIL PROTECTED]>:
>Sorry, I couldn't find any host named capsidi?e.com. (#5.1.2)
>
>--- Below this line is a copy of the message.
Note that it seems that the "to" was sent in iso-8859-1 (there is only
one non-recognized byte)
Thunderbird 2.0.0.9 sends the message and the server bounces it with:
>Hi. This is the qmail-send program at xxxxx.xxx.xxx.
>I'm afraid I wasn't able to deliver your message to the following
>addresses.
>This is a permanent error; I've given up. Sorry it didn't work out.
>
><[EMAIL PROTECTED]>:
>Sorry, I couldn't find any host named capsidi??e.com. (#5.1.2)
>
>--- Below this line is a copy of the message.
Note that it seems that Thunderbird is sending the "to" in utf-8 (the ñ
is two bytes)
It looks like it's a steep way up the road to make the server do the
right thing, because it looks like the clients send the data in the
codification they most like. any ideas?
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.
What are the two patches that need to be appied? (I don't see them in
the plugins documentation).
Regards, Marc
