On Tue, 1 Feb 2005, Matt wrote:

> I have even tried setting everything up per instructions such as:
> #######################################################################
> # ldbm database definitions
> #######################################################################
>
> database        ldbm
> suffix          "o=Internet Pipeline, c=CH"
> directory       /var/qmail/users
> rootdn          "cn=root, o=Internet Pipeline, c=CH"
> rootpw          secret
> index           objectclass,mail,mailAlternateAddress,uid  eq,sub
> index         accountStatus,mailHost,deliveryMode  eq
> index           default sub
>
> ==============================
>
> And it still doesn't work.. infact it tells me objectclass can not be
> a substring.... well now how on earth did it work for Andre???
>

You should only have to index 'eq' for objectclass. Here is my index
attributes, which seem to work pretty well:

index   objectClass     eq
index   cn              pres,eq,sub
index   mail            pres,eq,sub
index   uid             pres,eq,sub
index   mailAlternateAddress    eq
index   mailForwardingAddress   eq

I only index mailForwardingAddress so I can debug problems where customers
forget they forwareded mail from other accounts. Otherwise its not needed.
Also the sub indexes on mail and cn are also purely for command line
searches vs. what is needed for qmail to run efficiently. I found this
explanation of the index attributes (not easy to find!) which I found
helpful:

   1. pres -- A search for the presence of a particular attribute, e.g.,
'(objectClass=*)'
   2. eq -- A search for a particular attribute with a particular value,
e.g., '(uid=bjensen)'
   3. approx -- A sounds like search, like 'soundex' in SQL. I've never
actually seen this one used, but it would look something like
'{(sn~=Jensen)}'.
   4. sub -- This is a search for particular substrings. Because certain
types of substring searches are performed more than others, this option
can be decomposed into three sub-options. If you only specify sub, you get
indexes for all three.
         1. subinitial -- A search for an attribute with matching string
at the beginning, e.g., '(mail=bje*)'.
         2. subany -- A search with the wildcard somewhere in the middle,
e.g.,'(sn=j*sen)'.
         3. subfinal -- A search for an attribute with matching string at
the end, e.g, '(mail=*.com)'.


hope that helps.

Andreas

Reply via email to