Sam Varshavchik wrote:
Bowie Bailey writes:
The LDAP server is running on the same machine as Courier and I'm
submitting the message via the sendmail interface on the server. So
there are no firewalls (or other networking stuff) involved.
I'm doing the testing like this:
$ sendmail -f bow...@buc.com ttes...@example.net
$ sendmail -f bow...@buc.com ttes...@example.net
$ sendmail -f bow...@buc.com ttes...@example.net
450 Service temporarily unavailable.
ttes...@example.net: invalid address.
I'm wondering if the LDAP server forcibly closes idle connections.
After the first authentication request, each process keeps the
connection to the LDAP server open. The LDAP server may be closing
the idle connection after some period of time, which results in an
error when the same process eventually gets an authentication request.
Check the server's configuration for a similar setting, and adjust it.
Yes, the idle timeout is currently set at 30 seconds. I will increase
it to a couple of minutes and see what happens.
How do the authdaemon processes respond to lost ldap connections
(besides the obvious errors)? Does it simply reconnect for the next
attempt?
Will a timeout of a few minutes work, or do I need to increase it
further to avoid problems with the authdaemon?
20 messages in net.sourceforge.lists.courier-usersRE: [courier-users] authldap failing ...
