-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 After several months of developing rules and testing them with regex searches within my email client, I'm thinking it's time for me to actually begin using mass-check to test new rules.
Challenge: I'm a domain master on a shared domain server, and don't have access to local.cf or other central files. Everything I do is through $HOME/.spamassassin and my user_prefs. Would the following work? 1) create a $HOME/.spamassassin/mass-check directory. 2) In that directory, put my mass-check.cf, one spam file (I figure my most recent 5k or 10k spam), one ham file (similarly 5k or 10k ham messages), and a rules file. I then figure the execution command would be something like: > ./mass-check -c=$PWD -j=1 spam:mbox:$PWD/spamfile ham:mbox:$PWD/hamfile > Q1: Should this rules file be named local.cf or should it be user_prefs? Q2: Will mass-check ignore my primary user_prefs (which contains rules I don't want checked -- all I want to check are a few specific rules)? Q3: Are there any system-wide SA parameters I should include in $PWD/local.cf such that their lack would cause problems? (Note: I intentionally do not want to use --net in order to keep resource use to a minimum. Are there other parameters I should use/not-use in order to keep resource use down?) Any guidance would be appreciated. Bob Menschel -----BEGIN PGP SIGNATURE----- Version: PGP 8.0 iQA/AwUBP0L7AJebK8E4qh1HEQJ98QCgjzdeWKBnEHAU/rbc0qgMb3aMNjQAoIx/ Uoj+hw4co9CdPR2czEchC8fh =vWO+ -----END PGP SIGNATURE----- ------------------------------------------------------- This SF.net email is sponsored by Dice.com. Did you know that Dice has over 25,000 tech jobs available today? From careers in IT to Engineering to Tech Sales, Dice has tech jobs from the best hiring companies. http://www.dice.com/index.epl?rel_code=104 _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
