Nightly Mass-Check Runs

What?

Nightly MassCheck runs are the way people submit data on the effectiveness of current rules on their recent spam and ham. It is used to generate the very rule scores that determine the effectiveness of SpamAssassin (distributed via sa-update), and to evaluate rules via the RuleQaApp. The accuracy of SpamAssassin is directly related to the number of people contributing to nightly MassChecks.

This does not require sending us your email. Just logs of which rules hit your emails.

Usually a script is run from cron which automatically downloads the latest development version of SpamAssassin, runs it against your spam and ham, and then uploads a log of the results. One line per email, with a list of the SpamAssassin rules each email hit. Your actual email is not uploaded with this method.

An advantage to participating is that it makes SpamAssassin more accurate on your email.

How?

Unfortunately new masscheck contributors are not currently being accepted due to a security problem (bug 6694, which you probably can't see). You can still request an account, and you will be notified when it gets created.

1. Send an email to private@spamassassin.apache.org requesting an rsync account for nightly mass-checks. If you get no response, it can help to post to the public dev@spamassassin.apache.org mailing list.
2. Ensure SpamAssassin and its plugins are fully installed.
3. Download the auto-mass-check script (browse repo):

     git clone git://git.fedorahosted.org/auto-mass-check.git
     

4. Copy auto-mass-check/auto-mass-check.sh to ~/bin/
5. Copy auto-mass-check/auto-mass-check.cf to ~/.auto-mass-check.cf
6. Modify ~/.auto-mass-check.cf to point at your ham and spam folders. Be sure to configure properly for mbox (mbox) or Maildir (dir) folder formats. Leave the RSYNC options unchanged for now, because you will be running auto-mass-check in test mode at first.
7. Optionally set TRUSTED_NETWORKS and INTERNAL_NETWORKS in ~/.auto-mass-check.cf
8. Run auto-mass-check.sh.
   • Look in ~/masscheckwork/nightly_mass_check/ for ham-*.log and spam-*.log files. (Or weekly_mass_check on Saturday.)
   • Are the filenames good? They should be named something like ham-username.log or ham-net-username.log.
   • Read CorpusCleaning and HandClassifiedCorpora for guidelines of how to identify ham in your spam folder, and spam in your ham folder, and which messages you should be simply deleted.
   • If you move/delete messages, do not forget to "Compact Folder" to be sure they are actually gone.
   • Repeat auto-mass-check until you are certain both folders are cleaned.
9. Edit ~/.auto-mass-check.cf and set RSYNC_USERNAME and RSYNC_PASSWORD with values from step 1.
10. Run auto-mass-check.sh, which will upload your results.
11. Ask a more experienced participant (probably the person who recruited you) to check your results on the server. They can see the uploaded log files by running a command like rsync --old-d username@rsync.spamassassin.org::corpus/. You can also verify that your corpora show up on http://ruleqa.spamassassin.org/ - the green box near the top shows all included usernames.
12. If your upload looks good, then you're probably ready to automate nightly checks. Configure auto-mass-check to run as a cron job as your non-root user at or after 9AM UTC. (After weekly-versions.txt / nightly-versions.txt gets updated in rsync.spamassassin.org::corpus . If you run it earlier it will break things. )
    

(External documentation for auto-mass-check script.)

Alternative Methods

The easiest of all methods is to upload your corpora and let us process it for you: UploadedCorpora

The corpus-nightly script is a less maintained alternative to the auto-mass-check script: CorpusNightlyScript

Or you can do it manually: ManualNightlyMassCheck