The problem appears to have been because openldap-2.0.11 doesn't seem to deal
with refs very well when talking to itself via LDAPv2. I patched my
qmail-ldap to force use of LDAPv3 and it got better.
It might be nice if qmail-ldap tried LDAPv3 and then fell back to LDAPv2 if v3
wasn't available.
I would have written the patch myself, but since my C skills are so rusty, I
just change the '2' to a '3'.
When this gets implemented, I'd be more than willing to test it in my
opendap-2.0.11 site.
Chris
> From: "Chris Garrigues" <[EMAIL PROTECTED]>
> Date: Mon, 09 Jul 2001 11:08:50 -0500
>
> I just upgraded a bunch of systems to openldap-2.0.11 and had a problem with
> mail bouncing. Don't you love monday mornings after upgrading software?
>
> Anyway, I found entries like this in the ldap log:
>
> Jul 9 10:37:51 palm slapd[493]: conn=4592 op=0 BIND dn="" method=128
> Jul 9 10:37:51 palm slapd[493]: conn=4592 op=0 RESULT tag=97 err=0 text=
> Jul 9 10:37:51 palm slapd[493]: conn=4592 op=1 SRCH
>base="ou=people,o=virciomail,c=us" scope=2
>filter="(|([EMAIL PROTECTED])([EMAIL PROTECTED]))"
> Jul 9 10:37:51 palm slapd[493]: conn=4592 op=1 SEARCH RESULT tag=101 err=9
>text=Referral: ldap://10.1.10.2
> Jul 9 10:37:51 palm slapd[493]: conn=4592 op=2 SRCH
>base="ou=people,o=virciomail,c=us" scope=2
>filter="(|([EMAIL PROTECTED])([EMAIL PROTECTED]))"
> Jul 9 10:37:51 palm slapd[493]: conn=4592 op=2 SEARCH RESULT tag=101 err=9
>text=Referral: ldap://10.1.10.2
> Jul 9 10:37:51 palm slapd[493]: conn=4592 op=3 SRCH
>base="ou=people,o=virciomail,c=us" scope=2
>filter="(|([EMAIL PROTECTED])([EMAIL PROTECTED]))"
> Jul 9 10:37:51 palm slapd[493]: conn=4592 op=3 SEARCH RESULT tag=101 err=9
>text=Referral: ldap://10.1.10.2
> Jul 9 10:37:51 palm slapd[493]: conn=4592 op=4 SRCH
>base="ou=people,o=virciomail,c=us" scope=2
>filter="(|([EMAIL PROTECTED])([EMAIL PROTECTED]))"
> Jul 9 10:37:52 palm slapd[493]: conn=4592 op=4 SEARCH RESULT tag=101 err=9
>text=Referral: ldap://10.1.10.2
> Jul 9 10:37:52 palm slapd[493]: conn=4592 op=5 SRCH
>base="ou=people,o=virciomail,c=us" scope=2
>filter="(|([EMAIL PROTECTED])([EMAIL PROTECTED]))"
> Jul 9 10:37:52 palm slapd[493]: conn=4592 op=5 SEARCH RESULT tag=101 err=9
>text=Referral: ldap://10.1.10.2
> Jul 9 10:37:52 palm slapd[493]: conn=4592 op=6 SRCH
>base="ou=people,o=virciomail,c=us" scope=2
>filter="(|([EMAIL PROTECTED])([EMAIL PROTECTED]))"
> Jul 9 10:37:52 palm slapd[493]: conn=4592 op=6 SEARCH RESULT tag=101 err=9
>text=Referral: ldap://10.1.10.2
> Jul 9 10:37:52 palm slapd[493]: conn=-1 fd=64 closed
>
> when trying to send mail to [EMAIL PROTECTED] (who happens to be a
> mailalternateaddress)
>
> but the messages got bounced saying that the user was unknown.
>
> I removed the referral record from the database and it started working again.
>
> However, I really do want the referral records, so it would be nice if we
> could do the right thing here.
>
> W/o looking at the code, I imagine that if you get a return code, you simply
> assume that any records you got must be bad. However, that isn't the case
> when the return code is 9, and possibly in other cases as well.
--
Chris Garrigues http://www.DeepEddy.Com/~cwg/
virCIO http://www.virCIO.Com
4314 Avenue C
Austin, TX 78751-3709 +1 512 374 0500
My email address is an experiment in SPAM elimination. For an
explanation of what we're doing, see http://www.DeepEddy.Com/tms.html
Nobody ever got fired for buying Microsoft,
but they could get fired for relying on Microsoft.
PGP signature
