On Thursday, June 5, 2014 6:19:03 PM CEST, Viktor Dukhovni wrote:
I can't read or write Chinese, Japanese, Korean, Tamil, ... but
need to be able to set policy for such domain names from (e.g. white-list
them, ...).
Yes. Now, if check_sender_access contains UTF8, then what you paste to
whitelist an address is:
उदाहरण@उदाहरण.in ACCEPT
whereas if the domain uses a-labels, you need to use
उदाहरण@xn--p1b6ci4b4b3a.in ACCEPT
The first line is readable to people who understand hindi and has to be cut
and pasted by the rest of us. The second is halfway readable to people who
understand hindi, and has to be cut and pasted by the rest of us.
I can read/write a-labels.
Personally I've never had much luck reading or typing things like
xn--p1b6ci4b4b3a, and if I'm going to cut and paste I might as well paste
the human-readable form. At least that's readable if I understand the
writing system.
Maybe SMTP and DNS should have used the same wire representation. It's
too
late to change that now, though.
Indeed domain names in EAI SMTP (and in message headers) should
have been mandated to be a-labels with display conversion to UTF-8
left to MUAs.
If you don't mind, I'd rather not rehash that discussion. It was long and
tedious the first time, and I do not want to repeat it. I'll follow the RFC
as the finally ended up, not do what I thought was best. Perhaps e.g. 6532
section 3.2 contains the wrong decision about how to generate Received
fields, but the decision is clear and I really, really do not want to
repeat the discussion. Sorry.
Arnt
