Web design portfolio - 138 CHAPTER 4 ADDING CONTRIBUTED MODULES Spam
138 CHAPTER 4 ADDING CONTRIBUTED MODULES Spam Module Permissions The permissions structure of the Spam module is designed to let you divide your users into roughly three groups: those who can decide what content is or is not spam, those who are trustworthy and never create spam, and everyone else who cannot be trusted. The Access Spam Rating and Administer Spam Rating permissions can be given to user roles who will help train the filter and identify spam. When looking at content, they will be able to mark it either as spam or not spam, thus assigning a new score (1 or 99) and biasing the spam filter s future handling of similar content. As this is an essential activity, if you are to have an effective filter, you will want to make sure that you have trustworthy people in your community who have these permissions, so that spam content will be quickly identified and marked as such. However, keep in mind that anyone with these permissions can unpublish anything on your site simply by marking it as spam, so trust is essential. The Bypass Spam Filter permission can be granted to any user role who will never submit spam. This would certainly include user roles that receive the Access Spam Rating and Administer Spam Rating permissions. When users with the Bypass Spam Filter permission create content, it will not be passed through the Bayesian filter. The content can be marked as spam later, however. The only advantages to using this permission are a small performance gain, since less processing is done upon submitting content, and that no content will be falsely marked as spam for these users (a very small danger to begin with). It has the negative side effect that content from these users won t automatically train the filter. Thus, assigning this permission to too many users isn t a good idea. Filters for Content Types Select administer . settings . spam (admin/settings/spam) to see the configuration settings for the Spam module. The group of settings titled Filter gives you the chance to determine which content types will be eligible for spam filtering. As a rule of thumb, you should allow the Spam module to filter any content that can be created anonymously or by users whose trustworthiness cannot be guaranteed (that is, you don t know them personally). The options are as follows: Filter comments: This should be checked in most cases. There are known scripts for attacking Drupal sites where the URLs for nodes are systematically probed and comments are posted. The scripts craftily hit low-numbered nodes (low-numbered nodes are usually older content on most sites) and stop before becoming very conspicuous, in a bid to create comment spam but not be detected. Since these scripts target comments, it is advisable to enable this option. Filter open relays: This corresponds to the Distributed Server Boycott List method of spam filtering, described earlier. It uses the IP address of the user posting content and compares it to published lists of known spammers. Any content published from an IP address found on these lists will have a greatly increased chance of being marked as spam. Filter spammer URLs: This instructs the Spam module to pay greater attention to the URLs in content and afford them special treatment. The URLs in posts marked as spam will be branded as positive identifiers for spam content, and any new content containing the same URLs will be marked as spam.
Note: If you are looking for high quality webhost to host and run your jsp application check Vision christian web host services