Last modified: 2008-03-18 18:27:45 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T15411, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 13411 - wgSMTP does not reply correctly on error
wgSMTP does not reply correctly on error
Status: RESOLVED DUPLICATE of bug 11567
Product: MediaWiki
Classification: Unclassified
User preferences (Other open bugs)
unspecified
All All
: Normal critical (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-03-18 07:23 UTC by sancelot
Modified: 2008-03-18 18:27 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description sancelot 2008-03-18 07:23:30 UTC
I am using wgSMTP with auth mode.

If you made a mistake in wgSMTP setup,you should receive a mistake page
unfortunately this does not happens, because the error muistake message is a PEAR_Error object and can not be converted to string.

to solve this problem, you have to modify  includes/UserMailer.php as follow :

lines 160 :

	$err = $mail_object->send($dest, $headers, $body);
				if (PEAR::isError($err))
				{
					return $err->toString();
				}
				else return '';


my wrong wgSMTP setup was : 

$wgSMTP=array (
"host" => "mail.xxxxx.com",
"IDHost" => "xxxx.com",
"port" => "25",
"auth" => "true",
"username" => "sancelot@xxxx.com",
"password" => "pass",
);

and the right wgSMTP setup is (port and auth mistakes)  :
$wgSMTP=array (
"host" => "mail.xxxxx.com",
"IDHost" => "xxxx.com",
"port" => 25,
"auth" => true,
"username" => "sancelot@xxxx.com",
"password" => "pass",
);
Comment 1 Brion Vibber 2008-03-18 18:27:45 UTC

*** This bug has been marked as a duplicate of bug 11567 ***

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links