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
On Wednesday, June 4, 2014 11:16:51 PM CEST, Wietse Venema wrote:
* Postfix table queries are case-insensitive. I don't see any attempt
to implement that for UTF8 addresses. This leaves an ambiguity.
I looked at this now.
As I read the code, tables mostly map to lower case and then do a
On Thursday, June 5, 2014 10:36:49 AM CEST, Arnt Gulbrandsen wrote:
In my opinion the change to titlecase isn't worth it. There
aren't enough problems with lowercase() to justify such a
sweeping change. Also keeping lower case allows compiled tables
to survive upgrades/downgrades.
Worse:
Arnt Gulbrandsen:
On Wednesday, June 4, 2014 11:16:51 PM CEST, Wietse Venema wrote:
* Postfix table queries are case-insensitive. I don't see any attempt
to implement that for UTF8 addresses. This leaves an ambiguity.
I looked at this now.
As I read the code, tables mostly map to
This will require further research. If case canonicalization is as
complex as you describe then the correct result is likely to
differ from what real people expect. That is a security hole.
That was the case in the nineties, but by now the case folding algorithms
in unicode have won. They've
On Thu, Jun 05, 2014 at 02:24:38PM +0200, Arnt Gulbrandsen wrote:
But ? is nasty. I have even found two domains that differ only in ?/i, so
Postfix cannot treat them as equal.
Domains passed to lookup tables and match lists need to be in
a-label form. The remaining surprises with domains and
On Thursday, June 5, 2014 4:32:52 PM CEST, Viktor Dukhovni wrote:
Domains passed to lookup tables and match lists need to be in
a-label form.
That would make pcre almost impossible and mysql and pgsql lookups rather
inconvenient.
The a-label form of blåbærsyltetøy in a-label form is
On Thu, Jun 05, 2014 at 05:18:48PM +0200, Arnt Gulbrandsen wrote:
On Thursday, June 5, 2014 4:32:52 PM CEST, Viktor Dukhovni wrote:
Domains passed to lookup tables and match lists need to be in
a-label form.
That would make pcre almost impossible and mysql and pgsql lookups rather
Viktor Dukhovni:
Not too many people in Russia read Hebrew (right to left) or can
even cut and paste it reliably into a left to right context.
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
On Wednesday, June 4, 2014 3:23:24 PM CEST, Wietse Venema wrote:
Arnt Gulbrandsen:
On Wednesday, June 4, 2014 12:55:18 PM CEST, Wietse Venema wrote:
...
Yes. We must maintain compatibility with existing practice. Postfix
has always passed 8-bit headers and envelopes (localparts) for the
past
On Wednesday, June 4, 2014 6:58:43 PM CEST, Viktor Dukhovni wrote:
My impression is that UTF-8 domain names are are an MUA display
format issue.
There was tremedously tedious discussion of the approach you suggest, and
of many others. There was even a set of experimental RFCs issued. In the
On Wednesday, June 4, 2014 8:38:49 PM CEST, Wietse Venema wrote:
I'll read the RFCs carefully and see where it allows UTF8 in SMTP
command parameters and replies.
You'll do that, but I'll tell you anyway: The client may use it once the
server has issued an EHLO response containing SMTPUTF8,
Am 04.06.2014 19:48, schrieb Arnt Gulbrandsen:
Compliant SMTP servers only accept mail to/from EAI addresses if the
SMTP client uses the SMTPUTF8 form of the MAIL FROM command. The SMTP
client, in turn, only uses that form if the origin too used it.
The purpose of this feature is to
Arnt Gulbrandsen:
De/composition are pushed to the DNS. The SMTP part just says: Convert to a
IDNA a-labels in order to do the MX lookup, and otherwise don't mess with
the bytes you received. (My patch uses ICU to convert to a-labels.)
That is a mis-conception.
DNS is not the only interface
14 matches
Mail list logo
