My contact form getting spammed

Permalink
I have just started getting spam from my Concrete5 contact form.
i immediately turned on the captcha, but it made no difference I am still getting spam.
any ideas how to stop it?
I am getting about 20 a day.

I was going to paste the emails but realized how much smut was in it and decided not to, instead i have attached a text file. There are no links in the email which is weird, I am thinking it must be some kind of black hat SEO technique.

Other than disabling the contact form I don't see any workaround.

edit=========
my mistake, i thought i added captcha but i did not (i keep hitting enter when i submit changes , instead of clicking on the button - when i hit enter the changes are not saved)
I will see how it goes with captcha

1 Attachment

johnnyNui
 
frz replied on at Permalink Reply
frz
are these posts coming from the same IP? You could add that the site IP black list in the dashboard...

sounds like we should add flood control to the core...

any ideas from anyone else?
ScottC replied on at Permalink Reply
ScottC
make a hidden button named submit, then make the actual button named kittens or something, and also perhaps make a hidden text field named something suitable like salutation or something. If they click the hidden button to submit the form, then you know the contact form submission is a bot and delete it, if that hidden value is filled out, same thing.
johnnyNui replied on at Permalink Reply
johnnyNui
firstly , captcha stopped the spam.

and I checked the raw logs and the IP is different every time, so can't just block IP.
kirbydawg replied on at Permalink Reply
i am starting to have same problem kinda. ANY way to make it where when I receive a submission e-mail it has the IP address where it was sent? If i knew how to do that, i could handle the rest...where do I find the RAW files where i can find the IP? I know where to ban them, just not how to find them
Tony replied on at Permalink Reply
Tony
I ended up adding IP tracking to the guestbook cause I was having similar problems there, but it looks like they were spoofing the IP address, so I couldn't block by IP.