THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Once mass-check completes
| Wiki Markup |
|---|
If you're using mass-check to test your own rules, the next step is to run hit-frequencies: see [HitFrequencies] for details. Alternatively, if you're submitting data for a new scoreset, see \[RescoreMassCheck\], or \[NightlyMassCheck\] for the nightly QA test. |
Usage
| Wiki Markup |
|---|
mass-check \[options\] target ... |
-c=file | set configuration/rules directory |
-p=dir | set user-prefs directory |
-f=file | read list of targets from <file> |
-j=jobs | specify the number of processes to run simultaneously |
--net | turn on network checks! |
--mid | report Message-ID from each message |
--debug | report debugging information |
--progress | show progress updates during check |
--rewrite=OUT | save rewritten message to OUT (default is /tmp/out) |
--showdots | print a dot for each scanned message |
--rules=RE | Only test rules matching the given regexp RE |
--restart=N | restart all of the children after processing N messages |
--deencap=RE | Extract SpamAssassin-encapsulated spam mails only if they were encapsulated by servers matching the regexp RE (default = extract all SpamAssassin-encapsulated mails) |
...