Arnt Gulbrandsen:
> > How would a russian system admin effectively configure
> > manage tables/logging/queue management with domains in chinese or
> > hebrew script?
> 
> This is several questions. Two or three, I think.
> 
> One answer is that if an ISP wants to sell service to Chinese,

That is not the question. It's not about CUSTOMERS with an alien
script, It is about REMOTE SENDERS/RECEIVERS with domains in chinese
script. How does the russian adminstrator view/manage the mail
queue, how does he/she set/view/use rules in smtpd_mumble_restrictions.

I think the russian admin needs to choose how a command will render
domain names in access maps, address rewriting, mailq output.  UTF8
would be best for domain names in russian script, and ASCII would
be best for domains in chinese script. That will involve one
command-line option for postmap, postqueue, etc.

This is regardless of the representation that will be used internally
in Postfix tables (UTF9 or xn--mumble). With the mail queue we have
no choice - the representation is chosen by the sender.

> The other part is: What about queues/mail/tables involving the domains of 
> strangers on the net. If e.g. you have to add a separate queue to a 
> particular domain because mail to it disturbs others.
> 
> Since autodetecting on input is possible, I think that's how it has to be. 
> That will cater to postmaster preferences, to some degree.
> 
> I have no very strong opinion on the default format used for output. I know 
> my preference as user (look at LANG and use UTF8 if the locale uses it), 
> but I also know that as maintainer, I'd go with whatever causes less 
> support mail. Since you plan to use -DNO_EAI by default for one release 
> cycle you'll have enough time to decide.
> 
> > 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.
> 
> Yes. In a sense that's why I wanted to defer the autoconfiguration/format 
> choice; that might well involve merge conflicts and that would be even 
> worse in this change than usually.

EAI support will be added in small steps. It will definitely not be 
complete and it will be disabled by default (due to the external
dependency, with #ifdefs, in addition to main.cf configuration).

        Wietse

Reply via email to