Sam Varshavchik wrote:
> Bowie Bailey writes:
>
> > This connection worked:
> > authdaemond: received userid lookup request:
> > [EMAIL PROTECTED] authdaemond: authldap: trying this module
> > authdaemond: selected ldap protocol version 3
> > authdaemond: binding to LDAP server as #REMOVED#
> > authdaemond: using search filter:
> > (&(objectClass=CourierMailAccount)([EMAIL PROTECTED]))
> > authdaemond: one entry returned, DN:
> > [EMAIL PROTECTED],cn=Users,dc=example,dc=net
> >
> > This connection (5 seconds later) did not:
> > authdaemond: received userid lookup request:
> > [EMAIL PROTECTED] authdaemond: authldap: trying this module
> > authdaemond: using search filter:
> > (&(objectClass=CourierMailAccount)([EMAIL PROTECTED]))
> > authdaemond: ldap_search_st() failed
> > authdaemond: authldap: TEMPFAIL - no more modules will be tried
> >
> > Any ideas?
> >
> > If it makes any difference, the backend is the Fedora Directory
> > Server (v7.1, not the open source version).
>
> You'll need to look at the server's logs and see what they say.
>
> Also, search for any intermediate firewalls.
Did some more testing without finding much else.
When the connection succeeds, I can see it in the LDAP access logs.
When the connection fails, LDAP logs nothing at all in its access or
error logs.
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.
When it succeeds, I just kill it with Ctrl-C and try again. So above
you see two successful connections and then a failure. In that
particular run there were 12 successes, one failure, one success, and
then 3 failures. Sometimes it will succeed a few times before it
starts to fail and other times the first attempt will fail.
Is there any way to get more detailed debug information from authdaemon?
I'm already using DEBUG_LOGIN=2. Is there any other setting that would
give more information on the failure?
--
Bowie
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
