Using the LDAP configuration screen in the original release version of LISTSERV 15.5 may cause an error to be thrown when LISTSERV attempts to authenticate via LDAP, e.g.,


24 Apr 2008 13:23:53 >>> Error X'0000006B' looking up LDAP account <<<
24 Apr 2008 13:23:53  -> Severity: Error
24 Apr 2008 13:23:53  -> Facility: Generic error codes
24 Apr 2008 13:23:53  -> Abstract: Configuration error detected
24 Apr 2008 13:23:53 To   [ANONYMOUS]@LISTSERV.EXAMPLE.COM: ***BADPW***


In all cases we have seen, this will be due to a known bug found in the LDAP configuration screen which pre-populates a nickname of 'DEFAULT' for the first LDAP server configuration.  When entering a hostname in the LDAP_SERVER box and adding the connection, the following appears in sitecfg.file :


LDAP_SERVER_DEFAULT ldap.example.com

LDAP_PW_SERVERS DEFAULT


Unfortunately, 'DEFAULT' is never a valid nickname in the LDAP_SERVER line.  It should be:


LDAP_SERVER ldap.example.com

LDAP_PW_SERVERS DEFAULT


However, should you create an LDAP connection using a nickname other than "DEFAULT", the syntax would be valid:


LDAP_SERVER_EXAMPLE ldap.example.com

LDAP_PW_SERVERS EXAMPLE


This issue is fixed in the current version of LISTSERV.