Description: ------------ In the PEAR manual following declaration is specified: boolean Net_POP3::login (string $user string $pass boolean $apop) Am I right, that the last parameter $apop is not of type boolean, but of type "boolean or string"? By looking into the source code and following the parameter over serval function-calls, one can find a switch (in function _cmdAuthenticate) between the strings 'DIGEST-MD5', 'CRAM-MD5', 'APOP', 'PLAIN' , 'LOGIN', 'USER' or alternativly a false - value for this parameter. following code gives not the result as expected according to the documentation: $pop3->login($user, $pass,true); this would be the correct call: $pop3->login($user, $pass,"APOP"); Another thing: Since the last(?) update of the Net_POP3 class-documentation there are the wrong classnames (Net_Ping instead of Net_POP3) given on the overview page ( Net_Ping::Net_POP3() and so on) Reproduce code: ---------------

in my case neither $apop=true nor $apop=false worked. Only $apop "USER" was correct. I am not very familar with the POP3 protocol, so I only can try to obtain my opion by logical arguments: the login functions calls _cmdAuthenticat($user,$pass,$apop) with the critical parameter $apop (see pseudo code below). From _cmdAuthenticate($uid , $pwd , $userMethod = null first _getBestAuthMethod($userMethod) is called, and the result ist stored in $method, followed by a switch, which desides between serval string statements. Well, let's have a look how _getBestAuthMethod($userMethod)works in my case: Consider the case, that no $this->_capability['sasl'] was found, e.g. $serverMethods are set to array('APOP','USER'). Now consider, that I want to login with the 'USER'-method, according to the documentation this would be the boolean value false. The statement "if($userMethod !== null && $userMethod !== true )" would be true (because false is not of the same type as null), and false would be returned by the function. But this causes the default switch in the _cmdAuthenticate - function, which is an error-handler. But if $apop would be a string of the value "USER" everything works fine. function login($user, $pass, $apop = true) { ... $this->_cmdAuthenticate($user , $pass , $apop ) ... } function _cmdAuthenticate($uid , $pwd , $userMethod = null ) { ... $method = $this->_getBestAuthMethod($userMethod); ... switch($method) { case 'DIGEST-MD5': ... case 'CRAM-MD5': case 'LOGIN': case 'PLAIN': case 'APOP': case 'USER': default : ERROR } ... } function _getBestAuthMethod($userMethod = null) { ... if( isset($this->_capability['sasl']) ){ $serverMethods=$this->_capability['sasl']; }else{ $serverMethods=array('APOP','USER'); } ... if($userMethod !== null && $userMethod !== true ) { $methods = array(); $methods[] = $userMethod; return $userMethod; } ... }

As far as I can see, this bug is still very much alive in the latest release - v1.3.6. I can't use TRUE or FALSE as the third parameter for login(), I am forced instead to use 'APOP' or 'USER'. I am slightly concerned by the internal ID line at the top of the POP3.php file: $Id: POP3.php,v 1.2 2004/12/05 16:34:39 damian Exp $ Does this suggest the file is not v1.3.6 at all, but an older version? I would appreciate some other feedback - do other users find that the bug is fixed or not?

I ran into this problem today also. I had written a script to check multiple email boxes and it would only work with one of them. I ended up having to use the following to get it to work correctly: if(PEAR::isError( $ret=$myPop3->login($this->User,$this->Pass, 'USER') )){ echo "ERROR: " . $ret->getMessage() . "\n"; } using release v1.3.6

Bug is still not fixed. Tried to login with $pop3->login('user','pass', FALSE) error (using the toString() method on PEAR_ERROR object): pear_error: message=" is not a supported authentication method" using 'USER' instead of FALSE works perfectly. A fix in the docs or the method would be nice!