As reported at https://meta.wikimedia.org/w/index.php?title=Talk:MassMessage&oldid=6671296#not_working_in_ru.wiki, MassMessage appears to be broken (possibly blocked?) at ruwiki.
I don't see any relevant block log entries... perhaps AbuseFilter interference? Not sure.
Version: unspecified
Severity: normal
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=58258
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T60272 127.0.0.1, ::1, localhost, loopback, lo0 bugs (tracking) | |||
| Resolved | None | T60237 MassMessage is being affected by autoblocks on 127.0.0.1 |
https://ru.wikipedia.org/wiki/%D0%A1%D0%BB%D1%83%D0%B6%D0%B5%D0%B1%D0%BD%D0%B0%D1%8F:%D0%92%D0%BA%D0%BB%D0%B0%D0%B4/127.0.0.1 looks like 127.0.0.1 is blocked, and since autoblock is enabled it's being caught.
(In reply to comment #1)
Wow, great catch!
I'm curious whether any change should be made in MassMessage. Or perhaps we should simply update the documentation (e.g., [[m:MassMessage]] && [[mw:Help:Extension:MassMessage]]) to note that blocking localhost will cause this issue and then mark this bug as resolved/invalid.
Thoughts?
(In reply to comment #2)
(In reply to comment #1)
Wow, great catch!
I'm curious whether any change should be made in MassMessage.
We could potentially make the account ipblock-exempt regardless of the wiki's settings (enwiki gives ipblock-exempt to the bot group, ruwiki doesn't)
Or perhaps we
should simply update the documentation (e.g., [[m:MassMessage]] &&
[[mw:Help:Extension:MassMessage]]) to note that blocking localhost will cause
this issue and then mark this bug as resolved/invalid.
That would also work. Wikis really shouldn't be blocking 127.0.0.1 FWIW, it's just going to cause weird problems like this one.
Seems fixed. :-)
(In reply to comment #3)
Wikis really shouldn't be blocking 127.0.0.1 FWIW, it's just going to cause
weird problems like this one.
I filed bug 58258 to track this.
Just saw this on Wikidata (and about 5 more related log entries):
07:29, 5 May 2014 Delivery of "Tech News: 2014-19" to User talk:Eekiv failed with an error code of autoblocked
This is probably masking an issue in MediaWiki (I don't see anything that could have autoblocked 127.0.0.1 on wikidata...), but I don't think we should have deliveries fail because of this. If an admins goal is to block the bot, they can just block the account directly.
We could potentially make the account ipblock-exempt regardless of the
wiki's settings (enwiki gives ipblock-exempt to the bot group, ruwiki
doesn't)
I think this is the best thing to do for now.
(In reply to Kunal Mehta (Legoktm) from comment #7)
Just saw this on Wikidata (and about 5 more related log entries):
07:29, 5 May 2014 Delivery of "Tech News: 2014-19" to User talk:Eekiv
failed with an error code of autoblockedThis is probably masking an issue in MediaWiki (I don't see anything that
could have autoblocked 127.0.0.1 on wikidata...), but I don't think we
should have deliveries fail because of this. If an admins goal is to block
the bot, they can just block the account directly.
I wonder if it is not caused by yet another example of deferred update, something like bug 57815 ?
Change 132511 had a related patch set uploaded by Legoktm:
Give messenger user the 'ipblock-exempt' right
(In reply to Marcin Cieślak from comment #8)
I wonder if it is not caused by yet another example of deferred update,
something like bug 57815 ?
That would make perfect sense.