Home » Mail » Mail » Bug #3291

[2005-01-25 12:12 UTC] tchoudinov at yahoo dot com

Description:
------------
When I try to send mail using Mail::send with smtp backend it does not work. Method Send() reports "unable to connect to smtp server", but all the SMTP server credentials are correct.

Class Mail_smtp (extends class Mail)
File smtp.php
* @package Mail
* @version $Revision: 1.12 $

The code contains this error is somewhere here in function Mail_smtp::send(...):
----------------------------------------------------
if ($this->auth) {
$method = is_string($this->auth) ? $this->auth : '';

if (PEAR::isError($smtp->auth($this->username, $this->password,$method))) {
return new PEAR_Error('unable to authenticate to smtp server');
}
}

Reproduce code:
---------------
The same part of code in function Mail_smtp::send(...) in the previos version
* @package Mail
* @version $Revision: 1.3 $
was just:

----------------
if ($this->auth) {
if (PEAR::isError($smtp->auth($this->username, $this->password))) { return new PEAR_Error('unable to authenticate to smtp server'); }
if (PEAR::isError($smtp->identifySender())) { return new PEAR_Error('unable to identify smtp server'); }
}
----------------
This code works fine. Mail is sent.

[2005-01-25 12:15 UTC] tchoudinov at yahoo dot com

Note $smtp->identifySender() function call in the version that works fine. This call is absent in the last version of Mail_smtp::send() function.

[2005-01-26 16:33 UTC] tchoudinov at yahoo dot com

BTW I have Zend engine installed. May this is the problem.
PHP 4.3.9 (cli) (built: Sep 21 2004 14:04:30)
Copyright (c) 1997-2004 The PHP Group
Zend Engine v1.3.0, Copyright (c) 1998-2004 Zend Technologies
with Zend Extension Manager v1.0.4, Copyright (c) 2003-2004, by Zend Technologies
with Zend Optimizer v2.5.5, Copyright (c) 1998-2004, by Zend Technologies
with Zend Debugger v3.5.2, Copyright (c) 1999-2004, by Zend Technologies

[2007-02-01 17:24 UTC] chagenbu at php dot net

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.