Changes between Version 14 and Version 15 of SpamFilter

Timestamp:

Nov 1, 2006, 12:06:32 AM (18 years ago)

Author:

Christopher Lenz

Comment:

Add IP throttling strategy

SpamFilter

@@ -17 +17 @@
 
 The [source:sandbox/spam-filter/tracspamfilter/filters/ip_blacklist.py ip_blacklist] filter uses the third-party Python library [http://www.dnspython.org/ dnspython] to make DNS requests to a configurable list of IP blacklist servers.
+
+=== IP Throttling ===
+
+The [source:sandbox/spam-filter/tracspamfilter/filters/ip_throttle.py ip_throttle] filter limits the number of posts per hour allowed from a single IP.
+
+The maximum number of posts per hour is configured in [wiki:TracIni trac.ini]:
+
+{{{
+[spam-filter]
+max_posts_by_ip = 5
+}}}
+
+When this limit is exceeded, the filter starts giving submissions negative karma as specified by the `ip_throttle_karma` option.
+
+''(since version 0.2)''
 
 === Akismet ===
@@ -40 +55 @@
 === Bayes ===
 
-''TODO'' (The code in svn uses [http://spambayes.org SpamBayes], which is a logical choice.  It would make sense to use a custom tokenizer, however, rather than the email-centric one that is included with [http://spambayes.org SpamBayes].  The bigger issue is that some form of training is required (e.g. the API could be extended so that (optionally) authenticated users (and the other filters) could report contributions as spam (using automatic training to assume that everything else is ham); however, this is a complex change).  An alternative to this would be a script that could be periodically executed that would train all existing contributions as ham, and gather spam from an appropriate source.  If you decide to continue with this in the future, please don't hestiate to ask [mailto:spambayes-dev@python.org spambayes-dev] for help.
+''TODO''
+
+> (The code in svn uses [http://spambayes.org SpamBayes], which is a logical choice.  It would make sense to use a custom tokenizer, however, rather than the email-centric one that is included with [http://spambayes.org SpamBayes].  The bigger issue is that some form of training is required (e.g. the API could be extended so that (optionally) authenticated users (and the other filters) could report contributions as spam (using automatic training to assume that everything else is ham); however, this is a complex change).  An alternative to this would be a script that could be periodically executed that would train all existing contributions as ham, and gather spam from an appropriate source.  If you decide to continue with this in the future, please don't hestiate to ask [mailto:spambayes-dev@python.org spambayes-dev] for help.
 
 == WebAdmin Integration ==
@@ -58 +75 @@
 || Trac                  || Spam Filter ||
 || [milestone:0.10]      || latest ||
-|| [milestone:0.11]dev   || latest, but using the Genshi version of WebAdmin ||
+|| [milestone:0.11]dev   || latest ||
 
 See TracPlugins for instructions on building and installing plugins.