Last modified: 2010-05-15 15:37:55 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 3394 - SMTP Authentication Support (Wiki Configuration)
SMTP Authentication Support (Wiki Configuration)
Product: MediaWiki
Classification: Unclassified
Installer (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2005-09-08 04:23 UTC by Jamie Hari
Modified: 2010-05-15 15:37 UTC (History)
1 user (show)

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


Description Jamie Hari 2005-09-08 04:23:53 UTC
MediaWiki, as it stands does not lend itself to easy configuration of SMTP mail 
settings, especially where authentication (username and password) are required. In 
order to allow for this, one delves into php code. When 'localhost' SMTP mail 
servers are not available, a lot of current software allows for 'admin console' 
management of remote server SMTP configuration. (such as an ISP's email account) 
(i.e. User account, SMTP server, password, etc) An example of such a software is 

It would be extremely beneficial to allow for this type of setup in the initial 
installation or in an post-install 'admin console' of some sort.

Please email me at, for clarification or further 
Comment 1 Brion Vibber 2005-09-08 04:41:20 UTC
Set $wgSMTP if desired to use PEAR::Mail. See DefaultSettings.php for all 
configurable settings.

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