Option "Honeypot time limit" is ignored when Mollom is enabled for a form

I am seeing this as well. When commenting on a form with Mollom enabled (don't know if that has anything to do with it) and a 10 second Honeypot time limit, I see "please wait 40 seconds" when submitting my comments.

Is it possible that you previously commented on another page or filled out some other form too quickly, and Honeypot is just reacting to the fact that you've failed one form submission so far?

I need to test myself to make sure, but I think Honeypot just uses global flood results, so if you break the time limit once, your time limit won't be reset until another cron run when the flood table is updated to remove old flood entries.

Also, is this happening as an anonymous user, or a logged-in user?

I am testing this as an anonymous user and am able to reliably reproduce the issue. Here was my workflow, with actions performed as admin in square brackets:

1. [I disabled Honeypot time limit]
2. Submit a comment & complete Mollom verification - works
3. [I set the Honeypot time limit to 10 seconds]
4. View a node and click 'Add Comment'
5. Allow the comment form to finish loading in the browser
6. Start MySQL console and execute 'SELECT * FROM flood' - no entries were present for my IP address.
7. Count to 10, THEN submit a comment and complete Mollom verification - error:
   There was a problem with your form submission. Please wait 22 seconds and try again.
8. Go back to MySQL console and execute 'SELECT * FROM flood' - new entry present for my IP address (masked for privacy):
   

   +--------+----------+-----------------+------------+------------+
   | fid    | event    | identifier      | timestamp  | expiration |
   +--------+----------+-----------------+------------+------------+
   | 292546 | honeypot | 0.0.0.0         | 1381181986 | 1381185586 | 
   +--------+----------+-----------------+------------+------------+
   

So in addition to always blocking me even though I have respected the time limit, it blocks me for a seemingly arbitrary amount of time instead of enforcing the configured time limit. If I do wait the indicated time limit, the comment is posted successfully.

Perhaps this is related to Mollom? As after the first attempt (which always fails), Mollom knows I've entered the CAPTCHA correctly and does not make me enter one again.

Just tested submitting a comment with the mollom module disabled, it worked right away with the same Honeypot time limit of 10.

So, to clarify, does this problem only occur when Mollom is enabled at the same time as Honeypot? If so, what version are you using? I'll try to test and figure out what's going wrong.

That is correct, in my case at least. I'm not sure if that's also the case for @bigMuzzy. I have not tested for similar behavior with other CAPTCHA modules such as reCAPTCHA.

Okay, that helps; I'll investigate—I've been using the module alongside Mollom as well, but haven't run into this problem before... but both modules perform similar modifications on forms they run on, so I wouldn't be surprised if there was a conflict at some point!

I'm experiencing this problem without Mollum.

@kennyacock et all - what version of Honeypot are you using? There was a bug with the time limit with older versions...

I'm using version 7.x-1.17.

I can't reproduce locally, and for those using Mollom, I'm wondering if this was related to a bug fixed a couple months ago, and not directly to Mollom being used in tandem with Honeypot: #2277089: Time limit is double what it's supposed to be. Please reopen if you can reproduce with Honeypot 7.x-1.17 (and to @kennyacock—if this is still an issue for you, without Mollom, can you please open a new issue and describe all your settings and exactly what's happening on your site?).

Thanks!