From: Per Jessen on
Alejandro Cabrera Obed wrote:

> Dear all, I've just made a test from Gmail and my Thunderbird mail
> client sending a mail to a non-real IDN mail user:
>=20
> alejandro@a=C3=B1os.com.ar
>=20
> - My Thunderbird says: "An error ocurred while sending mail. Tha mail=

> servers responded: 5.1.3 Bad recipient address syntax" (THIS IS A
> SERVER RESPONSE)
>=20
> - The Gmail webmail says: "One o more mail address in "To:" box is no=
t
> recognized" (THIS IS A CLIENT RESPONSE)
>=20
> So, I think the IDN domain name support is not complete nowadays,
> neither by mail servers nor by mail clients. So it's not convenient
> the IDN mail implementation in this bad situation.
>=20
> What do you think about this matter ???

I think you're wrong - my thunderbird and my postfix does fine with
mails to and from @=C3=ABnidan.ch (a test domain I set about two years=

ago).=20


/Per Jessen, Z=C3=BCrich

From: Victor Duchovni on
On Thu, May 27, 2010 at 04:01:41PM -0300, Alejandro Cabrera Obed wrote:

> OK, this is in case of my Thunderbird Debian lenn package, but what
> about the Gmail syntax error warning ??? In Hotmail is the same, it
> tells me that the recipient address just must have 1-9, a-z and @
> characters....in this case with my IDN domain I wiil remain isolate of
> the Hotmail, Yahoo, Gmail world and it's not good !!!

Please waste no further time on this list. Postfix works with IDN. If
many clients still don't, that is NOT a Postfix issue. The clients
MUST (if they support IDN domains) send punycode encoded domains to
the SMTP server.

--
Viktor.

From: Per Jessen on
Per Jessen wrote:

>> So, I think the IDN domain name support is not complete nowadays,
>> neither by mail servers nor by mail clients. So it's not convenient
>> the IDN mail implementation in this bad situation.
>>=20
>> What do you think about this matter ???
>=20
> I think you're wrong - my thunderbird and my postfix does fine with
> mails to and from @=C3=ABnidan.ch (a test domain I set about two yea=
rs
> ago).

Correction - thunderbird doesn't work with IDNs. TB 3.0 is supposed to=

though.


/Per Jessen, Z=C3=BCrich

From: "Pat" on
>> Wietse, thanks...but in Postfix I have to work with the ?o?o.com.ar
>> domain name or with the xn--oo-yjab.gov.ar punycode domain name ???
>
> The MAIL CLIENT must tranform non-ASCII domain names before
> sending MAIL FROM or RCPT TO commands.

ICANN did not really consider the security and portability of IDNs before
permitting them. The reasons for this are many, and speak poorly to ICANN's
management structure. It is important to remember that ICANN's action does not
mean that end-users are prepared to accept mail from such domains, or that doing so
would be secure, much less that operating systems, libraries, and applications are
capable of dealing with IDNs safely.

Whether IDNs will ever be portable is a matter of debate. Right now they are in
early-alpha status i.e., not ready for production. This might be OK for some DNS
and SMTP implementations but for most production systems they pose too high of a
risk. The increase in complexity of each OS, lib, and app required to accommodate
IDNs is non-trivial. Widespread implementation would degrade security in and of
itself (because of the relationship between code size and security among other
factors).

Speaking only for myself, for the foreseeable future we are not interested in
experimental code and do not want to use a version of bind or postfix that cannot
be compiled to refuse IDNs.

Pat

From: LuKreme on
On 27-May-2010, at 13:36, Pat wrote:
>
> we are not interested in
> experimental code and do not want to use a version of bind or postfix that cannot
> be compiled to refuse IDNs.

If you refuse properly delegated IDNs then you are broken, pure and simple.

This is WHY punycode exists, as it requires no rewriting (or very little) of libraries to be UTF-8 clean.


--
There's nothing to do, so you just stay in bed [ah, poor thing] Why live
in the world when you can live in your head?