CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using Profiles (Moderator: Dave Greenberg) »
  • Blocking spam and cross-site subscriptions
Pages: [1]

Author Topic: Blocking spam and cross-site subscriptions  (Read 558 times)

daybell

  • I’m new here
  • *
  • Posts: 21
  • Karma: 0
    • Vermont Progressive Party
  • CiviCRM version: 4.1.5
  • CMS version: Drupal 6.26
  • MySQL version: 5.5.22
Blocking spam and cross-site subscriptions
January 28, 2011, 08:47:52 am
Have been searching a lot in both here and in the drupal forums, and haven't come up with anything that quite matches.

I am trying to put a block on my public drupal site which will start the double opt-in process to subscribe to a single public group (mailing list) on my private civicrm/drupal site, which lives on a different host. E-mail and group ID are required fields; first, last, and city are optional.

I am able to use the profile HTML snippet from civicrm, and place it in a custom block (using "add block") on the public site.  The URL however was immediately being hit by spambots.

To prevent this, I have tried and failed to:

Add a bogus hidden field, and then block the submit button if that field is populated with anything (no change in spam: I think the spambot is not actually using the form, just the URL and the unhidden fields)

Add captcha to the new block on the public site (captcha can only be placed on a form);

Create the subscription form with the webform module and use captcha (webform only will post the form to an e-mail address, not to a URL);

Obfuscate the URL using a javascript that rebuilds the URL from a few separate pieces (just can't get it to work, and I understand this wouldn't be an ideal solution anyway)

I should clarify that the bogus contacts never are added to the group (they don't get confirmed by e-mail), but the records are created and I don't want to have to spend time tracking down and deleting these contacts.

Thanks for any direction  or better suggestion.

Morgan

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using Profiles (Moderator: Dave Greenberg) »
  • Blocking spam and cross-site subscriptions

This forum was archived on 2017-11-26.