On Tue, Jan 25, 2005 at 04:12:22PM -0500, Ted Zlatanov wrote: > On 25 Jan 2005, [EMAIL PROTECTED] wrote: > > On Tue, Jan 25, 2005 at 10:51:08AM -0500, Ted Zlatanov wrote: > On 24 > Jan 2005, [EMAIL PROTECTED] wrote: > > >> > Openldap schema checking may not prevent creation of duplicate > >> > addresses as mailalternateaddress, but it should not be done. It > >> > is an error in the ldap tree. Perhaps the lookup utility should > >> > break with a proper warning instead of going with unpredictable > >> > result of returning just one of the two entries. (Mine returns > >> > both entries.) > >> > >> Agreed. Claudio, do you also think this is a bug in the lookup? > >> > > > > qmail-ldaplookup should always return all entries matched. So if only one > > is found it looks like a bug. Could you run it with -d 255 for more > > verbosity in qmail-ldaplookup (needs to be compiled with DEBUG). > > I can't do the recompile right now, but here's how you can duplicate > what I did. This may be a bug in OpenLDAP, by the way. I don't > know. > > 1) add address [EMAIL PROTECTED] to mailAlternateAddress TWICE (user A) > > 2) add [EMAIL PROTECTED] to user B > > 3) delete one of the two [EMAIL PROTECTED] addresses from user A > > Before 1, before 2, and before 3 qmail-ldaplookup behaved normally. > After 3, I only got one address. Here's the relevant info from LDAP: >
That sounds like a indexing bug of OpenLDAP. What version of OpenLDAP are you using and with which backend? -- :wq Claudio
