Posted by jeyro on October 5, 2009 at 10:51am
8 followers
Jump to:
| Project: | Spam |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | killes@www.drop.org |
| Status: | active |
Issue Summary
Does the spam module work for the contact form? I have not seen it mentioned and it does not appear in the list of possible content types in the Spam module's admin section. I suspect that it would not, since it appears to be a special type of node that is not treated as a content type.
For a site that does not have a lot of user-generated content, the contact form is *the* prime target for spam. The Spam module's functionality would be highly useful here.
In case the contact form is not included for Spam check, i like to make it a feature request.
Comments
#1
If you (or someone else) is interested in protecting the contact form (and others) from spammers, here's a list of spam-preventing modules.
#2
The contact form protection is very important imho, for many sites _it is_ the only open spot.
#3
There is a contributed module to do this already. The D6 version is in development, but working from what I understand.
http://drupal.org/project/gotcha
#4
Though apparently the new version no longer depends on Spam, I'm just now reading. That's a shame -- would've been a great SpamAPI module. I wonder how the spam filtering is being handled there.
Either way, contact form filtering would probably be very good as a contributed module. Right now, I think we're trying to stabilize the 6.x code base with our limited time; I know that my goal is ideally to have the code somewhat cleaned up and most of the big bugs fixed before 7.x is out.
#5
Respecting the decision to postpone this. For future consideration, this is a usability issue.
Captcha's ask irritating questions, I've seen people having serious difficulties with them, some versions may send content to third party sites, registered, for free or for a fee. If no sound is provided there are critical accessibility and depending on where you are, possibly legal issues. The math captcha and the current version of gotcha appear not to be stopping a good amount of spam, not even on low traffic sites.
The spam module does not visibly interfere with the user when filling a contact form, and it protects well.
To me, it did (still does) not appear as a major innovation to include the core contact form in its protection programme, while all other content and user input types are covered. In other words, why cover everything and leave one glaring hole? This as elaboration on my earlier post.
#6
If you feel like adding spam filtering to the contact form is not a "major innovation," please feel free to submit a contact content module and we'll be happy to add it. :) Like I said, it would be a good thing to add; I think we're in agreement on that. But we do what we can with limited volunteer resources. The one sure way to speed this particular issue is to submit code. I'm sure we will get to this -- it's just a matter of when.
Switching to "active" for now, just for visibility purposes in case someone wants to try their hand at submitting such a module.
#7
subscribing for future updates.
#8
working on this
#9
n.b. that although it's not made it into a stable release yet (at time of writing), some support for protecting the contact form was committed not long after killes posted above. It's in the current dev release.
#10
What killes did is now in 1.3.
Let us know whether this task is complete so we can close it.
Thank you.
Alexis
Update: fix the "not" to "now" as pointed out by mcdruid... (Oops!)
#11
AlexisWilke, I presume you meant "is now in 1.3"
I've switched a site using spam to protect the contact form from 6.x-1.x-dev to 6.x-1.3, and it seems to be working fine. Thanks.
+1 for being able to close this.
#12
See #1312432: When contacting customer through contact, i get this error code.