Re: postalAddress matching rule

[Quanah Gibson-Mount <quanah@zimbra.com>]

--On Tuesday, August 26, 2008 4:13 PM +1000 "Brett @Google" 
<brett.maxfield@gmail.com> wrote:

> Hello,
>
> I've just submitted a patch to help make the collect overlay
> (attribute inheritance) a bit more useful (ITS#5659).
>
> As part of my testing work for the above i once accidentally created a
> postalAddress attribute with two values. When i tried to remove the
> extra attribute value it failed, the error i got was something like
> that there is no matching rule for postalAddress, which if there
> really isn't then it's probably a reasonable thing for slapd to
> complain about, as it wont be able to tell the individual values of
> postalAddress apart.
>
> So to put it in a nutshell, i'm willing to have a go implementing a
> postalAddress matching rule, but i was wondering if anyone has any
> thoughts where i might begin, and/or any pointers as to which file(s)
> implement the matching rules.

Does the RFC proclaim a matching rule for postalAddress?  Because if it 
doesn't, there's no point in defining one. ;)  If an attr doesn't have a 
matching rule, you have to use a replace op rather than delete.

--Quanah

--

Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra ::  the leader in open source messaging and collaboration