RepuScore Deployment

We currently have two mechanism to participate in RepuScore. Organizations can either choose to submit the computed reputation to the us using a RepuScore Authority or choose not to submit the information for privacy concerns.
  1. An SpamAssassin plug-in deployed along with mysql database.
  2. Collecting log information and parse them into the database.

SpamAssassin Plugin

The SpamAssassin plug-in collects information about each email; i.e., it verifies whether an email is spam, and computes reputation every aggregation interval for all sender identities. The RepuScore plug-in collects information for either for authenticated email using standard SpamAssassin plug-ins for SPF and DKIM or for standard IP address. After sender identity's verification, the RepuScore plug-in transmits the email classification decision as a UDP packet to the local RepuServer.

The server module of the plug-in (a Perl module) maintains multiple forked instances to keep a few “hot” instances in memory to handle the normal load, while having the ability to fork a few additional instances based on the need. These processes capture the packets transmitted to them by the plug-ins’ client module and store the incoming data into a MySQL database. Using a cronjob, a script computes reputation every aggregation interval.

Collecting email log information and parse them into the database

If users do not have RepuScore plugin, we suggest organizations to collect the following information for their email records into a database:

Date; Sender IP addresses; Sender Domain; SPF Authenticated; DKIM Authenticated; Total Number of Spam; Total Number of Ham

Please download the format as an SQL file.

The Date is the date the email is received in the SQL Date format.
Sender IP address is an Integer.
Sender Domain is the name of the associated Domain.
"SPF Authenticated" or "DKIM Authenticated" fields is Boolean denoting the authentication pass or failure.
Total Spam and Total Ham is the number of emails received by the sender IP and domain name.


Please note that the primary key for the table is senderIP and senderDomain. For example, if you receive email from yahoo.com from two different IPs, they are two different entries in the database.