-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, we are using LDAP for mail routing with Postfix. We have moved the directory infrastructure and we can now do things without tearing down servers, but ... when a server is not able to perform a search it send back a bind referral.
How does Postfix react to this? I see this in the logs: Aug 30 18:10:27 correoe1 postfix/proxymap[19744]: warning: dict_ldap_connect: Unable to bind to server ldap://10.0.1.6:389 ldap://10.0.1.7:389 as cn=bind dn here: 9 (Partial results and referral received) Aug 30 18:10:27 correoe1 postfix/smtpd[19816]: NOQUEUE: reject: RCPT from mailfwd.nih.gov[128.231.90.106]: 451 4.3.0 <[email protected]>: Temporary lookup failure; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<relay.hub.example.com> It seems that postfix tries does not know what to do, as the system in the referral is not reachable (that is what might require second thoughts), but the firewall produces an immediate TCP reset, so 10.0.1.6 should, IMHO, be considered unreachable and 10.0.1.7 tried instead. Am I totally confused? Is this the intended flow? Thank you. - -- Victoriano Giralt Systems Manager Central ICT Services University of Malaga SPAIN - - A: Yes. | > Q: Are you sure ? |> >> A: Because it reverses the logical flow of conversation. |>> >>> Q: Why is top posting annoying in email ? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org iD8DBQFMe9lXV6+mDjj1PTgRAkaNAJ4787Vp+PZs+NUUM15nB7l4yLUdFwCgssG1 5UM7IkyVOL559vzwVeRO4A0= =3B7Y -----END PGP SIGNATURE-----
