Closed dni closed 7 years ago
Please carefully read https://github.com/magento-hackathon/HoneySpam/issues/25. Play around with the type and the name of the honeypot input field. Type email
and name email2
worked great for me.
Hi, type=email, name=email2, and similar things doesn't do the trick for me, the bot seems to notice the honeypot very well.
Any Ideas left? Going to switch to captcha as last resort don't like it though :(
No, then I do not have any other idea :/
You may have a look at Google "invisible" CAPTCHA. It is at least not as annoying as normal CAPTCHAs.
i wonder why the bot isnt trapped here, i use honeypots in all my other application and they work just fine.
Three possible reasons I can think of:
The other honeypot implementations are better.
my other application use a randomly generated input field like, which is different every time.
ii, iii.
<input autocomplete="off" id="rcktrittsformular-rSfhM5mn1pWy7qP" style="position:absolute; margin:0 0 0 -999em;" tabindex="-1" type="text" name="tx_form_formframework[form][rSfhM5mn1pWy7qP]">
Then I have no other idea, sorry.
do you think we can modify it to use an additional random field? hidden with just css? like in my example?
I cannot think of any reason why a random form field should work better.
maybe, the bots got smarter, filling out the forms multiple times, looking for the success page, and remember the fields which are not filled, to get a clue about the honey field.
which isn't really a hard thing to write for a bot. random fields would make this approach not really possible. also if there are 2 or more fields, the bot wouldnt be able to bruteforce find the honeyfield. (atleast not as easy as now).
but yeah, pure speculation, trying to think of a reason why my other honeypots are working fine. @
hi guys yesterday i installed this extension and i love the idea, problem is that for me still a lot of spam accounts get created, any idea what i can do? everything looks setup correctly insee die mhhs url in the hrml.