mike.lifeguard+bugs wrote:

Is this technically difficult to do, or is it simply that nobody has bothered yet?

mike.lifeguard+bugs wrote:

Product -> MeidaWiki extensions
Component -> Spam blacklist

mike.lifeguard+bugs wrote:

changed summary

At the moment is is impossible. The regular expressions of the configured blacklists are merged into one, and only then applied ("array_merge( $this->getLocalBlacklists(), $this->getSharedBlacklists() )".

To make this possible, each regular expressions should get a source ID (I would suggest an int from 0 to number of configured lists -1) based on the configured blacklists, and from there this should be passed on.

The coming to the user messaging, I could imagine that there is some message that can be used to add to the matching regular expression(s) (f.e. key 'spam-blacklist-hit-on-list-[123..n]'. It should allow for the location/URL of the list
to be added to the message as a parameter. If the specific message does not exist, it should probably allow for a fallback to key 'spam-blacklist-hit' or something.

• Bug 28243 has been marked as a duplicate of this bug. ***

Adding the equivalent bug for title blacklist and the tracking bug for stewards: spam blacklist is heavily used for cross-wiki maintenance and not being able to get reports of false positives is a major hinderance.
Also switching to "Normal" in analogy to Erik's bug 36940 because it's a proper bug, not a feature request; and restoring normal priority because it was lowered without reason (in a bulk bug change).