Le 06/04/2023 à 14:09, Emmanuel Fusté a écrit :
Le 06/04/2023 à 13:35, Ken Peng via Postfix-users a écrit :
On 2023-04-06 19:07, Jaroslaw Rafa via Postfix-users wrote:
I just now learned about the UTF8 thing, I would never think of using
non-ASCII characters in host/domain names :)
You can dig the UTF8 hostname, they are valid for query.
$ dig 腾讯.公司 ns +short
ns1.brandcloudns.com.
ns2.brandcloudns.com.
ns3.brandcloudns.com.
:)
Yes but no.... your UTF8 hostname is punicoded on your back before
going to the dns system.
dig 腾讯.公司 +noidnout +noall +question +answer ns
;xn--r70as2s.xn--55qx5d. IN NS
xn--r70as2s.xn--55qx5d. 3600 IN NS ns1.brandcloudns.com.
xn--r70as2s.xn--55qx5d. 3600 IN NS ns3.brandcloudns.com.
xn--r70as2s.xn--55qx5d. 3600 IN NS ns2.brandcloudns.com.
They are in fact plain acsii fully qualified hostnames, the utf8 is
just a displaying game.
As SMTP preclude idn, a conservative approach is that a client wanting
to pass utf8 fqdn hostname should encode it with idn as for the DNS/as
it get it from DNS.
In the context of HELO/EHLO, the DNS processed hostname should still
be plain ascii.
If we are ignoring the remaining IDNA2003 UTF8 domains corner case
(which are practically unusable in real world if there is still
sommes), there is no good reason to see utf8 fqdn in the HELO/EHLO
context.
And this corner case does not exist ... see Vicktor message. I should
had verified the content of IDNA2003 vs 2008.
Postfix is right.
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
