Mollom has not been catching a lot of my spam in my D7 site since I upgraded (from D6) and there seem to be several issues including not being able to connect to the server pretty frequently... but there is also an error which I haven't been able to figure out what to do about:

Notice: Undefined index: everything in mollom_admin_blacklist_form() (line 479 of /home/arianekca/domains/beta7.arianek.ca/public_html/sites/all/modules/mollom/mollom.admin.inc).

...which shows on http://westendgirl.ca/admin/config/content/mollom/blacklist

And from what I can tell, the blacklist isn't being used at all as I've filtered for things like "xanax" and (I'd figure I wouldn't even need to add drugs like this to the blacklist?) they're still getting through.

Also, if I try and remove an old entry from the blacklist (migrated from the D6 version) I get the error "An error occurred upon trying to remove the item from the blacklist." And in the log entries in Drupal I see the following details for this:

Error 404: Not Found
Error 404: Not Found

Request: GET http://rest.mollom.com/v1/blacklist/97e9a0ad7c8059ae908049a7a7a12b04/97e9a0ad7c8059ae908049a7a7a12b04-text-everything-spam-http:

Request headers:
  Accept = 'application/xml, application/json;q=0.8, */*;q=0.5'
  Authorization = 'OAuth oauth_consumer_key="97e9a0ad7c8059ae908049a7a7a12b04", oauth_version="1.0", oauth_nonce="46e2843cc3baddcc1e2fec0009c5e3d3", oauth_timestamp="1347322211", oauth_signature_method="HMAC-SHA1", oauth_signature="BaGGVvOUwFJmcNSfk0Bt1NOOlFg%3D"'
Response: 404 Not Found
  code = '404'
  message = 'The requested blacklist item does not exist!'

And...

Failed to remove (%context) from blacklist.
Error 404: Not Found

Request: GET http://rest.mollom.com/v1/blacklist/97e9a0ad7c8059ae908049a7a7a12b04/97e9a0ad7c8059ae908049a7a7a12b04-text-everything-spam-http:

Request headers:
  Accept = 'application/xml, application/json;q=0.8, */*;q=0.5'
  Authorization = 'OAuth oauth_consumer_key="97e9a0ad7c8059ae908049a7a7a12b04", oauth_version="1.0", oauth_nonce="3c20b1d0e83949ae71fcf53d9e39f90a", oauth_timestamp="1347322213", oauth_signature_method="HMAC-SHA1", oauth_signature="iAeYCrH%2Br5Hyr%2BebVtppwBTcKmc%3D"'
Response: 404 Not Found
  code = '404'
  message = 'The requested blacklist item does not exist!'
Error 404: Not Found

Request: POST http://rest.mollom.com/v1/blacklist/97e9a0ad7c8059ae908049a7a7a12b04//delete

Request headers:
  Accept = 'application/xml, application/json;q=0.8, */*;q=0.5'
  Content-Type = 'application/x-www-form-urlencoded'
  Authorization = 'OAuth oauth_consumer_key="97e9a0ad7c8059ae908049a7a7a12b04", oauth_version="1.0", oauth_nonce="b776df3146fef6e8587ee6d87cc844f0", oauth_timestamp="1347322213", oauth_signature_method="HMAC-SHA1", oauth_signature="VvPaKVQbKMYmnERs%2FqTquuKVYbE%3D"'
Failed to remove (%context) from blacklist.

Possibly these are totally unrelated but I am not sure, so thought may as well include all the info in one spot - if you want me to split that into a separate issue lemme know!

Thanks!

Comments

Just tried reinstalling and this is still happening - getting tons of spam (30+) each day even though it appears that Mollom is catching some spam... it's stuff that I think it should be catching, like clearly spam with lots of links, pharmaceutical names etc.

[not useful details - removed]

My installation of Mollom behaves exactly the same, arianek. I'm getting 30+ spam submissions per day, despite the fact that most of the submissions include keywords that I've added to my blacklist (cialis, viagra, cigarettes, hair loss, louis vuitton, casino, blackjack, etc.).

I too receive errors when trying to add items to the blacklist - typically takes 2-3 repeated form submissions before my keyword is added successfully.

Plus, the number of spam submissions is reduced to zero if I toggle the setting When Mollom is down or unreachable to Block all form submissions. This suggests that Mollom servers must be unavailable a huge percentage of the time! I've submitted a separate issue about that.

It seems the Mollom "free service" is hardly doing anything to cut down spam on my site. If I felt confident Mollom was effective, then maybe I'd be wanting to pay for the service, but at this point I'm not confident at all that it would be worth it. And I'd be much more inclined to shell out closer to 5€/month as I am not going to be earning any kind of an income from my blog to be able to afford a fee as high as 30€/month.

paul2 - good to know it's not just me! I also see many times when Mollom is down in my logs, *but* this is happening when it's functioning as well.

For what it's worth, Mollom is still catching a ton of spam - in the 5 minutes that it was disabled on my site when I reinstalled it, I got about 50 spams! So it's still effective, just not as effective as it used to be, and the blacklist entries are (I'm now certain) being completely ignored. I suspect it has to do with the error posted in the summary, but haven't the vaguest idea what to do about it!

Title:blacklist error Blacklist items not found despite being displayed in the UI
Priority:Normal» Major

I thought this might have been cached locally but reviewing the code it's not. So it looks like a bug in the service itself.

Mollom backend engineers are actively working on a fix for this.

The problem only applies to sites that used the XML-RPC API before (i.e., Mollom module 1.x series) and upgraded their clients to the REST API (i.e., Mollom module 2.x series).

The module's code is correct. It's the Mollom API that returns bogus/incompatible values.

A solution is expected to happen this week.

Version:7.x-2.2» 7.x-2.x-dev
Status:Active» Fixed

Sorry, I forgot to follow up here.

This issue has been fixed in the server-side Mollom backend/API. Therefore, the error should have disappeared automatically on all client sites.

Note that the transition works in one way only though:

  1. Blacklist entries created with the old 1.x series of the module (using XML-RPC) can be fully accessed and managed from the 2.x series of the module (using REST).
  2. Downgrading from 2.x to 1.x is not supported — you will see PHP notices on the blacklist administration pages for each blacklist entry that has been created in the 2.x series (using the REST API).

The 1.x series of the Mollom module is discontinued anyway though. If you haven't updated to 2.x yet, please consider to do so. :)

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.