It would be helpful (without having to figure out how in the heck PCRE works) to have an option for having anything submitted in UTF-8 automatically flagged as probable spam.

I've got a large amount of Chinese language comment spam appearing in my approval queue and none of it is being caught by the spam module. In looking at the "edit comment" page for the comment (www.example.com/comment/edit/XXX), you can see that it is being submitted in UTF-8.

Since the average user (anonymous or registered) is likely to want to submit their comment in UTF-8, it seems to me that having a way to detect and assign a "probability" to comments submitted this way would be a valuable addition to this modules capabilities.

CommentFileSizeAuthor
UTF8commentspam.png18.32 KBfriskya

Comments

friskya’s picture

Whoops!

I mean't "unlikely" to want to submit their comments in UTF-8

Sorry about that!

friskya’s picture

Title: comment spam being submitted in utf-8 is missed by 4.7.x - 2.1.4 (not available as a choice in the version dropdown) » comment spam being submitted in UNICODE is missed by 4.7.x - 2.1.4 (not available as a choice in the version dropdown)

Sorry - just discovered that my understanding of non-english language character display was wrong.

What I'm trying to say is, anything submitted in the format (& # 12362;) (had to add the whitespace to prevent it from displaying as it's Chinese equivalent) has a better than average chance of being spam, so an option to filter for anything submitted in that format would be helpful. I don't thing the average drupal user is going to know how to create a "perl compatible regular expression" right off.

jeremy’s picture

Version: 4.7.x-1.x-dev » 5.x-1.x-dev
Status: Active » Postponed

I am postponing this functionality until I have time to work on the 5.x-2.x version of the module.

jeremy’s picture

Version: 5.x-1.x-dev » 5.x-3.x-dev
Priority: Critical » Normal
Status: Postponed » Active

The 5.x-3.x development branch allows for easier development of custom filters, such as this one. Re-opening against this development branch.

jeremy’s picture

Status: Active » Postponed

Postponing this request until someone comes along with a patch. This should be implemented as a plug-in, not as a patch to the core spam module.

killes@www.drop.org’s picture

Status: Postponed » Closed (won't fix)

Nobody was interested after all.