You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spamassassin.apache.org by Apache Wiki <wi...@apache.org> on 2014/04/01 03:48:01 UTC

[Spamassassin Wiki] Update of "TxRep" by Ivo Truxa

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Spamassassin Wiki" for change notification.

The "TxRep" page has been changed by Ivo Truxa:
https://wiki.apache.org/spamassassin/TxRep?action=diff&rev1=40&rev2=41

Comment:
some more text

  
  More details are available on the [[http://truxoft.com/resources/txrep.htm|TxRep POD page]]. 
  
- 
  == How Does It Work? ==
  
  The algorithm works using a local database of entries. Each entry has a key formed by 
@@ -51, +50 @@

  to adjust the impact of the reputation, which may be useful when starting off.
  
  
- == How do I whitelist/blacklist someone? == 
+ == How do I train spam/ham? ==
+ 
+ In exactly the same way (and in the same time) as you train spam and ham to the Bayesian 
+ SA system:
+ 
+  * `sa-learn --spam file`
+  * `sa-learn --ham file`
+ 
+ It means that if your server is set up to use IMAP folders, webmail, or other tools for
+ training SpamAssassin, the TxRep reputation will be adjusted at senders of all the trained
+ messages anytime you use it. More details about the algorithm are available in 
+ [[http://truxoft.com/resources/txrep.htm#LEARNING-SPAM-HAM|TxRep POD]].
+ 
+ Additionally, you can also enable the [[http://truxoft.com/resources/txrep.htm#txrep_autolearn|txrep_autolearn]] 
+ option. In such case, when the message scores trigger SpamAssassin's auto-learn process,
+ TxRep will add or subtract additional points to the stored reputation.
  
  
+ == How do I whitelist/blacklist someone? ==
  
- ==== Utility ====
+ Blacklisting/whitelisting can be done through the standard command line options of 
+ SpamAssassin:
  
+  * `spamassassin --add-addr-to-blacklist=foe@spam.biz`
+  * `spamassassin --add-addr-to-whitelist=friend@ham.org`
+ 
+ You can repeat the whitelisting/blacklisting multiple times - either to make it stronger,
+ or to negate previous whitelisting by blacklisting (or vice versa).
+ 
+ It is necessary to understand that whitelisting/blacklisting through TxRep is not the 
+ same as whitelisting/blacklisting in a cf file, using the whitelist_from or blacklist_from
+ directives. TxRep whitelisting/blacklisting only adjusts the plain email address mean 
+ reputation by 100 points. However, the reputation of the plain email address is only one 
+ part of the overall reputation, and the influence of the reputation is also limited by the
+ txrep_factor. It means, the whitelisting or blacklisting through TxRep may still be 
+ overridden.
+ 
+ More details can be found in [[http://truxoft.com/resources/txrep.htm#BLACKLISTING-WHITELISTING|TxRep POD]].
+ 
+ == Database Storages & Utilities ==
+ 
- TxRep uses the same storage handler as its predecessor AWL, therefor TxRep DB format 
+ TxRep uses the same storage handlers as its predecessor AWL, therefor TxRep Berkeley DB 
- backend files can be examined, pruned, and manipulated with the same tools as at AWL:
+ format backend files can be examined, pruned, and manipulated with the same tools as at AWL.
+ See also the [[https://wiki.apache.org/spamassassin/AutoWhitelist|AWL page]] for some more details
  
   * [[http://spamassassin.apache.org/full/3.4.x/doc/sa-awl.html|'sa-awl']] - simple tool available in the distribution package
   * [[http://www.real-world-systems.com/mail/sa-heatu.html|'sa-heatu' v1]] - external enhanced tool
   * [[http://truxoft.com/resources/sa-heatu.v4.02.tar.gz|'sa-heatu' v2]] - newer, enhanced version
  
- See also the [[https://wiki.apache.org/spamassassin/AutoWhitelist|AWL page]] for some more details 
+ When using the SQL storage type, multitude of SQL tools can be used for the same purpose - for example
+ PhpMyAdmin for MySQL, PhpPgAdmin for Postgresql, etc.
  
+ Although requested, there is currently no Redis storage handler available for AWL or TxRep, but MySQL 
+ storage tuned with the MEMORY engine, or InnoDB engine with a sufficiently big innodb_buffer_pool parameter, 
+ or together with the MySQL memcache plugin, would offer similar performance as Redis, while allowing 
+ much better vertical and horizontal scalability (it would work better for both bigger tables and multiple 
+ concurrent accesses as well).
+ 
+  
+