Bowie Bailey writes:
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 [EMAIL PROTECTED] [EMAIL PROTECTED] > $ sendmail -f [EMAIL PROTECTED] [EMAIL PROTECTED] > $ sendmail -f [EMAIL PROTECTED] [EMAIL PROTECTED] > 450 Service temporarily unavailable. > [EMAIL PROTECTED]: invalid address.I'm wondering if the LDAP server forcibly closes idle connections. After the first authentication request, each process keeps theconnection 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?
Increase it to at list a couple of hours. With the LDAP server on the same machine, the reasons why you want an inactivity timeout are no longer relevant.
pgpZVUUFZMLQB.pgp
Description: PGP signature
