THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
mass-check also takes other options to control whether network tests are run, whether multiple processes are run in parallel, how the output is presented, etc.; read the comments at the top of the file for details. Here's some key bits:
Using network tests
for For mass-checks for scoresets 1 or 3, using network tests, you need to provide the --net switch. Ensure Net::DNS, Mail::SPF::Query, Razor, pyzor Pyzor and DCC are installed.
Network tests are slow unless you use the -j switch to allow mass-check to start multiple parallel scanning processes.
...
-n | no date sorting or spam/ham interleavingBR |
--after=N | only test mails received after time_t N (negative values are an offset from current time, e.g. -86400 = last day) or after date as parsed by Time::Parsedate (e.g. '-6 months') BR |
--before=N | same as --after, except received times are before time_t N BR |
--cache | Use cached information about atime (generates files in corpus area)BR |
--all | don't skip big messages BR |
--head=N | only check first N ham and N spam (N messages if -n used) BR |
--tail=N | only check last N ham and N spam (N messages if -n used) BR |
...