Topic on Project:Support desk

The Guestbook extension changes the $wgSpamRegex value! This I have overseen because it is not a typcial spam protecion extension. In addtion to that, the DefaultSetting.php sets $wgSpamRegex to an empty array and the manual here claims true as default value. This gave me some additional confusion.

I recently updated this wiki here to V1.31. Now I'm doing this and that to polish up the visual appearance a little bit. Doing so, I discovered an odd behaviour:

Every page that contains the term spam, actually three pages which are dealing with this topic, are rejected by a dubios spam protection filter. This filter claims, that

The page you wanted to save was blocked by the spam filter. This is probably caused by a link to an external site.

and

The following text was found by the spam filter: Spam

And I have to admit: Yes, the term is used on this pages. But to describe something around the topic spam. As far as I know, this is far away from being spam itself.

Subsequently there is really no way to circle around this blocking. Even as Sysop my hands are tied!

So does anybody know a way to stall this edgy spam filter jumping on a harmless four letter word like spam, in particular one will only explain this term.

Many thanks for an answer in advance!

This functionality is not built into MediaWiki. Try disabling some extensions or talk to your host?

Well, in case of this rejected content the de.json file from the languages/i18n folder provides exactly the shown error messages. There are three messages called spamprotectiontitle, spamprotectiontext and spamprotectionmatch. The content of that messages, in addition with the bad word spam, is displayed instead of saving the article. The en.json file also contains the english pendant of this messages, starting in line 3020 of en.json (MW 1.31.3).

Also this messages are mentioned here: Manual:$wgSpamRegex

But it is not changed in my LocalSettings.php. It comes from DefaultSettigs.php as $wgSpamRegex = [];.

The explanation in above mentioned manual also describes my experience: even a Sysop fails to save if that error occurs.

Bingo. I added $wgSpamRegex = false; to my LocalSettings.php. Now the pages which cotains the term spam can be saved again. In contrast to Manual:$wgSpamRegex, which claims that the default value is false, the MW 1.31.3 DefaultSetting.php gives me an empty array instead. Maybe this causes confusion or some weird fallback solution with some odd regex from elsewhere gets suddenly effective.

could you file a task in phabricotor for this bug?

I managed to do this: https://phabricator.wikimedia.org/T228081

I hope that this is what you mean. It's the very first time that I have tried to file something in phabricator.

yes, thanks.