Page History

...

The algorithm works using a local database of entries. Each entry has a key formed by the identificator, and optionally the IP address it originated at, and the DKIM signature. It contains a TOTAL score of messages and a COUNT of messages. The MEAN score is TOTAL/COUNT. Each sender is identified by several IDs: the From email address in combination with the originating IP block, the standalone From email address (without any IP), the domain name of the From address, the full IP address, and the HELO name. Each of these ID types has a configurable weight factor when calculating the overall sender's reputation. The overall txrep_factor can be adjusted in the configuration to adjust the impact of the reputation, which may be useful when starting off.

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 TxRep POD.

Additionally, you can also enable the 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?

...

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 TxRep POD.

Database Storages & Utilities

TxRep uses the same storage handler handlers as its predecessor AWL, therefor TxRep Berkeley DB format backend files can be examined, pruned, and manipulated with the same tools as at AWL:AWL. See also the AWL page for some more details

• 'sa-awl' - simple tool available in the distribution package
• 'sa-heatu' v1 - external enhanced tool
• 'sa-heatu' v2 - newer, enhanced version
  

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).See also the AWL page for some more details