[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#7157) UTF-8 support for "mail" attribute



--On Tuesday, February 07, 2012 9:03 PM +0000 alfiej@opera.com wrote:

> Full_Name: Alfie John
> Version: 2.4.23
> OS: Debian Squeeze
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (220.245.36.226)
>
>
> When searching for Chinese names in the "to:" field under Thunderbird, I
> see asserted_value_validate_normalize() not returning LDAP_SUCCESS in
> filter.c. This is because the "mail" attribute in core.schema is of type
> "IA5 String" but the Chinese name falls outside the character set.
>
> The work around I have is to modify the "mail" attributetype in the
> core.schema from:
>
>   attributetype ( 0.9.2342.19200300.100.1.3
>     NAME ( 'mail' 'rfc822Mailbox' )
>     DESC 'RFC1274: RFC822 Mailbox'
>     EQUALITY caseIgnoreIA5Match
>     SUBSTR caseIgnoreIA5SubstringsMatch
>     SYNTAX 1.3.6.1.4.1.1466.115.121.1.26{256} )
>
> to:
>
>   attributetype ( 0.9.2342.19200300.100.1.3
>     NAME ( 'mail' 'rfc822Mailbox' )
>     DESC 'RFC1274: RFC822 Mailbox'
>     EQUALITY caseIgnoreMatch
>     SUBSTR caseIgnoreSubstringsMatch
>     SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{256} )
>
> Dieter Kl?nter pointed out on the openldap-technical mailing list that
> this breaks RFC-5322. However Charles T. Brooks suggests:
>
>   Non-english character sets are going to become part of
>   hostnames and DNS.  That's inevitable.
>
>   Mail addresses are based on DNS hostnames.
>
>   Ergo, mail attributes will one day need to support all possible
>   characters.
>
> Given that, I think the above changes to core.schema seem worthwhile.

I would say then, that the proper place to bring this up would be with the 
IETF.

--Quanah


--

Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra ::  the leader in open source messaging and collaboration