> returns. Sometimes an ldap connection doesn't work because > the server which ldap server connects to, is temporarily busy > and unavailable. The client could try again after 1 second and it > will work again..
Hm... I think this isn't exactly an ASSP issue, more an LDAP server one; the fact that the LDAP server is unresponsive at times may be a sign of some other issues (e.g. insufficient hardware, network overloading...) so I think you'd better solve the issue on the LDAP server side; at any rate, some possible workarounds may be either Switch ASSP to VRFY/EXPN recipient checks; to do so you'll need to use a special syntax in your "localDomains" (see the ASSP GUI for details) to tell ASSP which server to use for VRFY/EXPN for a given domain, you'll also need to enable VRFY/EXPN on the SMTP server used for such a check or Install a second LDAP server keeping a copy (e.g. rsync or whatever) of the LDAP data and set it up so that only your ASSP box(es) will use it, this way it won't "lock" due to overload and ASSP won't have issues HTH ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
