Arnt Gulbrandsen:
> On Friday, June 6, 2014 1:55:37 AM CEST, Wietse Venema wrote:
> > Postfix is meant to be used by human operators anywhere on the
> > Internet. Therefore, the postqueue/postmap/etc. tools will have
> > to accept non-ASCII domain names from a human operator in either
> > UTF-8 form and xn--mumble form, and they will have to convert those
> > forms into their stored form. Those tools will also have to render
> > non-ASCII domain names in their stored form, or convert them into
> > UTF-8 or xn--mumble form on request by the human operator.
>
> I looked at this now and would like to defer this work until the first
> patch has been accepted and I can work against a new canonical source tree.
> OK?
In that case, don't bother writing code. Instead, share/discuss
your design decisions/recommendations. Does it make sense to fold
case with table lookups? How do we deal with table lokups when the
same domain can show up in different forms at different stages of
email handling (client or server name, mail from/rcpt to domain,
mail headers). How would a russian system admin effectively configure
manage tables/logging/queue management with domains in chinese or
hebrew script?
I will be working bits and pieces of the patch into Postfix over
the remainder of 2014. This is invasive stuff and it needs to be
done right.
Wietse
