Hi At some point during yesterday afternoon I suddenly ceased to be able to log in to courier to check my mail. Outgoing (authenticated) SMTP also stopped working but incoming SMTP with no auth is still working. As far as I can tell, no one could have been logged in and made any config changes when it stopped working.
Setup: Debian Woody with Linux 2.4.22 Courier 0.37.3 Courier-IMAP 1.4.3 slapd 2.0.23 As it appeared to be an auth problem, I bumped up the slapd loglevel and got this in syslog from a courier restart and: # courierauthtest [EMAIL PROTECTED] <password> <--snip--> Jun 15 14:03:26 fenrir authdaemond.ldap: authdaemon: modules="authldap", daemons=5 Jun 15 14:03:26 fenrir courierd: Loading STATIC transport module libraries. Jun 15 14:03:26 fenrir courierd: Courier 0.37.3 Copyright 1999-2000 Double Precision, Inc. Jun 15 14:03:26 fenrir courierd: Installing [0/0] Jun 15 14:03:26 fenrir courierd: Installing uucp Jun 15 14:03:26 fenrir courierd: Installed: module.uucp - Courier 0.37.3 Copyright 1999-2000 Double Precision, Inc. Jun 15 14:03:26 fenrir courierd: Installing local Jun 15 14:03:26 fenrir courierd: Installed: module.local - Courier 0.37.3 Copyright 1999-2000 Double Precision, Inc. Jun 15 14:03:26 fenrir courierd: Installing esmtp Jun 15 14:03:26 fenrir courierd: Installed: module.esmtp - Courier 0.37.3 Copyright 1999-2000 Double Precision, Inc. Jun 15 14:03:26 fenrir courierd: Installing dsn Jun 15 14:03:26 fenrir courierd: Installed: module.dsn - Courier 0.37.3 Copyright 1999-2000 Double Precision, Inc. Jun 15 14:03:26 fenrir courierd: Initializing uucp Jun 15 14:03:26 fenrir courierd: Initializing local Jun 15 14:03:26 fenrir courierd: Initializing esmtp Jun 15 14:03:26 fenrir courierd: Initializing dsn Jun 15 14:03:26 fenrir courierd: Started ./courieruucp, pid=5071, maxdels=4, maxhost=4, maxrcpt=16 Jun 15 14:03:26 fenrir courierd: Started ./courierlocal, pid=5075, maxdels=10, maxhost=4, maxrcpt=1 Jun 15 14:03:26 fenrir courierd: Started ./courieresmtp, pid=5078, maxdels=40, maxhost=4, maxrcpt=100 Jun 15 14:03:26 fenrir courierd: Started ./courierdsn, pid=5081, maxdels=4, maxhost=1, maxrcpt=1 Jun 15 14:03:26 fenrir courierd: queuelo=200, queuehi=400 Jun 15 14:03:26 fenrir courierd: Purging /var/lib/courier/msgq Jun 15 14:03:26 fenrir courierd: Purging /var/lib/courier/msgs Jun 15 14:03:26 fenrir courierd: Waiting. shutdown time=Tue Jun 15 15:03:26 2004, wakeup time=Tue Jun 15 15:03:26 2004, queuedelivering=0, inprogress=0 Jun 15 14:03:58 fenrir slapd[4483]: daemon: conn=7 fd=9 connection from IP=127.0.0.1:1186 (IP=:: 34049) accepted. Jun 15 14:03:58 fenrir slapd[4570]: conn=7 op=0 BIND dn="" method=128 Jun 15 14:03:58 fenrir slapd[4570]: conn=7 op=0 RESULT tag=97 err=0 text= Jun 15 14:03:58 fenrir slapd[4569]: conn=7 op=1 SRCH base="o=hosting,dc=outpost,dc=org,dc=uk" scope=2 filter="([EMAIL PROTECTED])" Jun 15 14:03:58 fenrir slapd[4569]: conn=7 op=1 SEARCH RESULT tag=101 err=0 text= Jun 15 14:04:13 fenrir slapd[4483]: daemon: conn=8 fd=15 connection from IP=127.0.0.1:1187 (IP=:: 34049) accepted. Jun 15 14:04:13 fenrir slapd[4570]: conn=8 op=0 BIND dn="[EMAIL PROTECTED],O=OUTPOST.ORG.UK,O=HOSTING,DC=OUTPOST,DC=ORG,DC=UK" method=128 Jun 15 14:04:13 fenrir slapd[4570]: conn=8 op=0 RESULT tag=97 err=0 text= Jun 15 14:04:13 fenrir slapd[4569]: conn=8 op=1 UNBIND Jun 15 14:04:13 fenrir slapd[4569]: conn=-1 fd=15 closed As far as I can tell, this appears to be OK? ...but I get: Temporary authentication failure from module authdaemon Authentication FAILED! Running: # courierauthtest [EMAIL PROTECTED] works fine and returns my maildir details etc, but *not* the first time I run it after restarting courier (or, more specifically, authdaemond). Pointing Ethereal at lo, I can see the search results coming back OK, and when I try courierauthtest with my password I can see authdaemond successfully binding to my record with my password, but I still get an auth failure. slapd returns identical Search Entry and Search Result packets when it is queried immediately after an authdaemond restart and when it is tried a second, third, fourth time; the only difference being that authdaemond has to bind before searching when it has just been restarted. I'm assuming that my login fails because authdaemon opens a new TCP connection to bind to my record, but fails to recognise that it has bound successfully. It then unbinds, and thus doesn't get a chance to successfully reuse the connection as it does when fetching user details. I have no idea what's going on - any advice would be very much appreciated. thanks... -Stuart Stuart Yarrow --------------------------------- http://fingamidi.sourceforge.net/ http://www.outpost.org.uk/ ------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
