Page History

...

  wget http://people.apache.org/~jm/devel/Mail-SpamAssassin-3.1.0-pre3pre4.tar.gz
  tar xvfz Mail-SpamAssassin-3.1.0-pre3pre4.tar.gz
  cd Mail-SpamAssassin-3.1.0
  perl Makefile.PL < /dev/null
  make

  cd masses
  mkdir spamassassin
  rm -f spamassassin/*
  echo "bayes_auto_learn 0" > spamassassin/user_prefs
  echo "lock_method flock" >> spamassassin/user_prefs
  echo "bayes_store_module Mail::SpamAssassin::BayesStore::SDBM" >> spamassassin/user_prefs
  echo "use_auto_whitelist 0" >> spamassassin/user_prefs

  nohup ./mass-check --bayes --net -j 4 --restart=400 --learn=35 --reuse \
        --after=1072933200 <targets>

<targets> is the list of directories, mboxes, etc., like
spam:dir:~/Mail/spam. See the comments at the top of "mass-check" for details.

Do not use --reuse if the targets you are using have not been scanned by SpamAssassin with network tests enabled, or if scanned with SA, but have configured that scanner to run with -L, or you have disabled common network tests or SPF. This is because it relies on the presence of the X-Spam-Status line to pick up hits on those rules, and currently cannot detect those conditions.

This takes *ages* to run. -j 4 controls the number of processes to use; 4 should be OK for a single-processor machine, since most of the time they'll be waiting for network results to arrive. If you have adequate RAM and don't mind the load, you can use -j 6 or -j 8. There's not much benefit in going higher than -j 8.

...

If you have an unusual network layout, you may need to specify
trusted_networks and/or internal_networks in the
spamassassin/user_prefs file. But SA should be able to infer it in most cases. If you get less than a 10% or 15% spam hit rate for RCVD_IN_XBL, then you might have needed to use these configuration parameters. (Since RCVD_IN_XBL is reused, this won't help you much now...)

Once it finishes:

...

A good way to tell is if you see no SPF_PASS results – SPF will not be used if the message passes through one or more trusted relays.

Once it finishes, check that the results are sane. See CorpusCleaning to remove any result lines that deal with misclassified or corrupt messages.

...

Then submit your results!

  USER="[whatever your username is]"
  RSYNC_PASSWORD="[whatever your password is]"
  export RSYNC_PASSWORD

  rsync -Pcvuzb ham.log $USER@rsync.spamassassin.org::submit/ham-bayes-net-$USER.log
  rsync -Pcvuzb spam.log $USER@rsync.spamassassin.org::submit/spam-bayes-net-$USER.log

...

The results for this run will need to be in by Monday July 11thFriday July 22nd (tentatively). If you're still running then, submit what you have so far and beg for more time. We may be pushing it out a little further anyway depending on how things go