Brian Candler wrote: > On Wed, Aug 09, 2006 at 07:32:53PM +0530, Dhawal Doshy wrote: >> Hello List, >> >> My environment: >> Centos 4.3 x86 >> courier-authlib-0.58-1 >> courier-imap-4.1.1-1 >> openldap-2.2.13-4 >> >> Is it possible to have different errors when: >> a. Password is incorrect >> b. Account is locked / inactive / disabled using "LDAP_FILTER >> (accountStatus=active)" > > That would be hard, because the LDAP_FILTER is sent to the LDAP server, and > would simply mean that no matching LDAP record was found. It wouldn't be > possible to tell whether this was because the user did not exist, or because > they existed but had accountStatus!=active > > However if you set the account options (disableimap=1, disablepop3=1) you > can get something similar: > > -ERR POP3 access disabled for this account. > * BYE IMAP access disabled for this account. > > It still doesn't say *why* the account was disabled, but at least it's > different. > > Regards, > > Brian.
Excellent.. i added the following. /etc/authlib/authldaprc: LDAP_AUXOPTIONS disableimap=accountStatus /etc/authlib/authdaemonrc: DEFAULTOPTIONS="disableimap=1" Now i get a proper error as required. One more thing.. can i say use 'active/inactive' rather than '0/1' without changing the source. Thanks Brian, now i need to have horde/imp reflect the proper error. - dhawal ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Courier-imap mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
