Last modified: 2012-10-29 16:39:58 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 T19787, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 17787 - Allow blocking email for IPs
Allow blocking email for IPs
Status: RESOLVED DUPLICATE of bug 18860
Product: MediaWiki
Classification: Unclassified
User blocking (Other open bugs)
All All
: Normal normal with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: SWMT
  Show dependency treegraph
Reported: 2009-03-04 15:43 UTC by Mike.lifeguard
Modified: 2012-10-29 16:39 UTC (History)
3 users (show)

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


Description Mike.lifeguard 2009-03-04 15:43:37 UTC
When blocking IPs, wpEmailBan is not available. Please make it so - then we can block IPs which are generating malicioius email resets or other email issues. This should also take the anon-only param and apply it. If set to anon-only email should be blocked only for IPs (which I guess will affect only password resets). If it's not set, this should block emailing from registered users on that IP as well.
Comment 1 Mike.lifeguard 2009-03-04 15:45:21 UTC
See also bug 17487. Really, both these should be done.
Comment 2 MA 2009-04-04 18:59:11 UTC
Blocked IP adresses in a project can't use the remind password feature.

"Login error: Your IP address is blocked from editing, and so is not allowed to use the password recovery function to prevent abuse."

As I said on the problem is that those vandals switcht between projects and abuse the feature in all of them. A limit per day of reminders should be set as well a feature to block an IP to use this feature globally. Cheers.
-- dferg
Comment 3 Nakon 2009-08-06 05:02:28 UTC

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

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