Bookworm
03-16-2004, 03:34 AM
I ran across this a while back, and now have hit it again. And spent almost as much time re-researching it.
with the "auto" test option for available scanners, which is default for the QMR install, you get clamuko_scanner, and fast_spamassassin.
That's fine for non-microsoft email clients, which can filter on a header line. However, microsoft clients tend to be really stupid, and are easiest to filter on the subject line.
Two ways to get around it.
1) edit /var/qmail/bin/qmail-scanner-queue.pl
find the line spamc_options
it has the options " -c, -f"
Remove -c. That makes it verbose, rather than fast. That's the quick and dirty option, because it forces the qmail-scanner to use the local.cf preferences for scanning. However, it's slower.
2) during the configuration of qmail-scanner-queue, add this to the ./configure line
--scanners "clamuko_scanner,fast_spamassassin=SPAM"
(you can use most any non-ISO style character. Hypens are out, as are pound symbols (#) asterisks, and so forth). I'm using S_P_A_M, as it's not likely to show up in a 'normal' email, whereas "Hey, do you think this is spam" would show up quite often if you were a consultant like I am. )
My recommendation with 2) above would be to run the initial ./configure the 'normal' way. (with the scanners running on auto). Make certain that 'clamuko_scanner' and 'fast_spamassassin' are both seen by the ./configure script. Then do the --install with the --scanners line added to it.
I feel REALLY stupid, as I updated qmail-scanner, blew away the -working- configuration I already had had, and couldn't figure out why my local.cf file was being totally ignored (again). Hopefully, now that I've made notes in my installation file, I'll never hit THAT wall again.
I also hope that I've saved someone else from hitting it.
BW
P.S. - qmail-scanner is now up to 1.21
with the "auto" test option for available scanners, which is default for the QMR install, you get clamuko_scanner, and fast_spamassassin.
That's fine for non-microsoft email clients, which can filter on a header line. However, microsoft clients tend to be really stupid, and are easiest to filter on the subject line.
Two ways to get around it.
1) edit /var/qmail/bin/qmail-scanner-queue.pl
find the line spamc_options
it has the options " -c, -f"
Remove -c. That makes it verbose, rather than fast. That's the quick and dirty option, because it forces the qmail-scanner to use the local.cf preferences for scanning. However, it's slower.
2) during the configuration of qmail-scanner-queue, add this to the ./configure line
--scanners "clamuko_scanner,fast_spamassassin=SPAM"
(you can use most any non-ISO style character. Hypens are out, as are pound symbols (#) asterisks, and so forth). I'm using S_P_A_M, as it's not likely to show up in a 'normal' email, whereas "Hey, do you think this is spam" would show up quite often if you were a consultant like I am. )
My recommendation with 2) above would be to run the initial ./configure the 'normal' way. (with the scanners running on auto). Make certain that 'clamuko_scanner' and 'fast_spamassassin' are both seen by the ./configure script. Then do the --install with the --scanners line added to it.
I feel REALLY stupid, as I updated qmail-scanner, blew away the -working- configuration I already had had, and couldn't figure out why my local.cf file was being totally ignored (again). Hopefully, now that I've made notes in my installation file, I'll never hit THAT wall again.
I also hope that I've saved someone else from hitting it.
BW
P.S. - qmail-scanner is now up to 1.21