Benutzeranmeldung z34b19ry0

sowas sollte man nach Möglichkeit von seinem Blog fern halten
Stop Forum Spam gibt da Auskunft
Auch wenn man sein Blog öffentlich zugänglich machen will, sollte man die Sache ein bisschen unter Kontrolle halten.
Aus diesem Grund benutze ich das gleichnamige Plugin; hält mir Spammer und auch andere Bösewichter fern (hoffe ich zu mindest)

Zitat von hhuelder

Wenn ich das richtig sehe, laufen die Plugins so, dass sie die IPs von Leuten, die sich anmelden wollen, mit externen Datenbanken vergleichen. Was ich nicht erkennen konnte, ist, ob sie die Listen herunterladen (was ja die Performence des Blogs beeinträchtigt) oder die IP zum Vergleich übermitteln (was m. W. in Deutschland verboten ist).
Ein leichtes Dilemma...

Zitat

The Stop Spammers Plugin is installed and working correctly.
Version 4.3
How the plugin works Eliminates 99% of spam registrations and comments. Checks all attempts to leave spam against Stop Forum Spam, Project Honeypot, and BotScout, DNSBL lists such as Spamhaus.org, known spammer hosts such as Ubiquity Servers, disposable email addresses, very long email address and names, and HTTP_ACCEPT header. Checks for robots that hit your site too fast, and puts a fake comment and login screen where only spammers will find them. In all the plugin uses 15 different strategies to block spammers.
How the plugin works:
This plugin checks against StopForumSpam.com, Project Honeypot and BotScout to to prevent spammers from registering or making comments. The Stop Spammers plugin works by checking the IP address, email and user id of anyone who tries to register, login, or leave a comment. This effectively blocks spammers who try to register on blogs or leave spam. It checks a users credentials against up to three databases: Stop Forum Spam, Project Honeypot, and BotScout. Optionally checks against Akismet for Logins and Registrations.
Optionally the plugin will also check for disposable email addresses, check for the lack of a HTTP_ACCEPT header, and check against several DNSBL lists such as Spamhaus.org. It also checks against spammer hosts like Ubiquity-Nobis, XSServer, Balticom, Everhost, FDC, Exetel, Virpus and other servers, which are a major source of Spam Comments.
Rejects very long email addresses and very long author names since spammers can't resist putting there message everywhere. It also rejects form POST data where there is no HTTP_REFERER header, because spammers often forget to include the referring site information in their software.
The plugin will install a "Red Herring" comment form that will be invisible to normal users. Spammers will find this form and try to do their dirty deed using it. This results in the IP address being added to the deny list. This feature is turned off by default because the form might screw up your theme. Turn the option on and check your theme. If the form (a one pixel box) changes your theme presentation then turn the feature off. I highly recommend that you try this option. It stops a ton of spam.
The plugin can check how long it takes a spammer to read the comment submit form and then post the comment. If this takes less than 5 seconds, then the commenter is a spammer. A human cannot fill out email, comment, and then submit the comment in less than 5 seconds. This is the best way to stop spam.
Limitations:
StopForumSpam.com limits checks to 10,000 per day for each IP so the plugin may stop validating on very busy sites. I have not seen this happen, yet. The plugin will not stop spam that has not been reported to the various databases. You will always get some comments from spammers who are not yet reported. You can help others and yourself by reporting spam. If you do not report spam, the spammer will keep hitting you. This plugin works best with Akismet. Akismet works well, but clutters the database with spam comments that need to be deleted regularly, and Akismet does not work with spammer registrations.
API Keys:
API Keys are NOT required for the plugin to work. Stop Forum Spam does not require a key so this plugin will work immediately without a key. The API key for Stop Forum Spam is only used for reporting spam. In order to use the Project HoneyPot or BotScout spam databases you will need to register at those sites and get a free API key.
History:
The Stop Spammers plugin keeps a count of the spammers that it has blocked and displays this on the WordPress dashboard. It also displays the last hits on email or IP and it also shows a history of the times it has made a check, showing rejections, passing emails and errors. When there is data to display there will also be a button to clear out the data. You can control the size of the list and clear the history.
Cache:
The Stop Spammers plugin keeps track of a number of spammer emails and IP addresses in a cache to avoid pinging databases more often than necessary. The results are saved and displayed. You can control the length of the cache list and clear it at any time.
Reporting Spam :
On the comments moderation page, the plugin adds extra options to check comments against the various databases and to report to the Stop Forum Spam database. You will need a Stop Forum Spam API key in order to report spam/
Network MU Installation Option :
If you are running a networked WPMU system of blogs, you can optionally control this plugin from the control panel of the main blog. By checking the 'Networked ON' radio button, the individual blogs will not see the options page. The API keys will only have to entered in one place and the history will only appear in one place, making the plugin easier to use for administrating many blogs. The comments, however, still must be maintained from each blog. The Network buttons only appear if you have a Networked installation.
Debugging:
If the plugin is having trouble it drops a file in the plugin’s directory named sfs_debug_output.txt. If the file is produced it will appear at the bottom of this page along with a button to delete it. Common errors include many which are not really an issue. From time to time you will see an error that reports that PHP could not redirect a page. This happens on some systems where the spammer is rejected, but the access denied screen does not appear correctly. I believe this is caused by data in the spam comment.
If you do not want to see any errors you can search in the plugin code for the line that contains "debug=true;" and change the true to false, so the line is "debug=false;" (a semicolon at the end is required by PHP). I have set the plugin to report problems by default (debug=true;).
Please report any errors that you see.
Requirements :
The plugin uses the WP_Http class to query the spam databases. Normally, if WordPress is working, then this class can access the databases. If, however, the system administrator has turned off the ability to open a url, then the plugin will not work. Sometimes placing a php.ini file in the blog's root directory with the line 'allow_url_fopen=On' will solve this.
The Stop Spammers plugin is ON when it is installed and enabled. To turn it off just disable the plugin from the plugin menu..
You may see your own email in the cache as spammers try to use it to leave comments. You may have to white list your own email if that is the case, to keep the plugin from locking you out.
There is a button that allows you check access to the StopForumSpam database from the plugin Options page. This will tell you if the host allows opening of remote URL addresses. Please check your network access to the StopForumSpam database before reporting that the plugin doesn't work. The problem may be your host configuration.
[HR][/HR] For questions and support please check my website BlogsEye.com.

Alles anzeigen

wenn das die Datenschutzregeln missachtet, gibt es weiter Alternativen

hhuelder:

Zitat

Bei mir haben die angemeldeten User ja zunächst die niedrigsten Rechte, können also im Prinzip nicht mehr, als unangemeldete Besucher.

Aber als registrierter Nutzer kann er u.U. Kommentare ohne vorherige Freischaltung erstellen und somit Deinen Blog zuspamen.