AVH First Defense Against Spam
[resolved] Project Honey Pot Termination type threshold (6 posts)

  1. MickeyRoush
    Posted 4 years ago #

    I have a question about the setting under 3rd Party Options.
    Under the Project Honey Pot section is a setting "Termination type threshold" where there are nine possible settings.

    Search Engine
    Suspicious & Harvester
    Comment Spammer
    Suspicious & Comment Spammer
    Harvester & Comment Spammer
    Suspicious & Harvester & Comment Spammer

    Is this in order of least specific to most specific? How exactly do these settings work? For example: Does selecting Suspicious match all of those that are beneath it? Or are these conditional? Meaning that the suspected must meet exactly what I select?

    Sorry, this is just a bit confusing for me, as I would like to terminate all suspicious, harvesters, & comment spammers.

    Any explanation would be greatly appreciated.


  2. petervanderdoes
    Plugin Author

    Posted 4 years ago #

    It's a trickle down, which as I'm answering your question is actually incorrect. A harvester isn't necessarily a comment spammer. It should be that selecting Harvester would trigger:

    • Harvester
    • Suspicious & Harvester
    • Harvester & Comment Spammer
    • Suspicious & Harvester & Comment Spammer

    I'll work on that soon.

  3. MickeyRoush
    Posted 4 years ago #

    @ petervanderdoes

    Thanks for the quick reply.

    The Default is set at 'Comment Spammer'. Is that what you recommend? Would any setting be more 'powerful' than another?

    Thanks again for any reply.

  4. petervanderdoes
    Plugin Author

    Posted 4 years ago #

    If you set it to Comment Spammer, that's what I run my blog on, you check for
    Suspicious & Comment Spammer
    Harvester & Comment Spammer
    Suspicious & Harvester & Comment Spammer

    as well. So any IP that could be a Comment Spammer will be blocked.
    The other two options Suspicious and Harvester won't post a comment, according to Project Honey Pot, they are a nuisance but that's about it.

    Personally I would never block an IP that is Suspicious, that term is to vague. Harvester would be more "powerful" but like I said, an IP declared as Harvester by itself shouldn't post comments.

  5. MickeyRoush
    Posted 4 years ago #

    That helps. Thanks!

  6. AlphaWolf
    Posted 3 years ago #

    Sorry to open this back up... But I still find it a bit confusing. Is there any way to block IPs that are Comment Spammers or Harvesters, or any combination of those two with something else? If I understand you correctly setting "Harvester & Comment Spammer" requires the IP to be both of those things in order to be blocked.

    There's a specific reason I want to block both -- and the reason is that the honey pot link is only given on the block page. In order to help Project Honey Pot keep track of whether IP's are still misbehaving (and improve the project for everyone), we need to give Spammers/Harvesters as many opportunities as possible to misbehave. My use of AVH F.D.A.S is less "keep spam off my sites" and more "let's kill spam altogether by helping Project Honey Pot as much as possible".

    A bit off-topic, but it would also be great if the plugin could randomly generate the hidden honey pot links using Project Honey Pot's suggestions, and include these one every page rather than just the block page. I'm using an SMF mod called httpBL that does this if you'd like some inspiration.

    As a closing note, I think AVH F.D.A.S. is fantastic, and I haven't received even a single spam comment on any WordPress site since activating the plugin with StopForumSpam and Project Honey Pot.


Topic Closed

This topic has been closed to new replies.

About this Plugin

  • AVH First Defense Against Spam
  • Frequently Asked Questions
  • Support Threads
  • Reviews

About this Topic