Shwetar (sent by Nabble.com) wrote:
Hi Matte,
Yeah I already have qmail-scanner1.20 up and running... and I have logcheck
installed which keeps mailing me periodically the scanner log contents...
Sep 29 13:58:18 myserver qmail-scanner[27731]:
Policy:Bad_MIME_Break:RC:0(212.241.78.57): 0.528588 3370
[EMAIL PROTECTED] [EMAIL PROTECTED] Teeth_bleaching_made_easy
<[EMAIL PROTECTED]> 1128016430.27733-0.myserver:2435
orig-myserver112801643076827731:3370
This was blocked by qmail-scanner itself. There is no mention of
spamassassin at all in that snippet. Do you see anything like:
Sep 29 15:06:20 external qmail-scanner[29244]:
Clear:RC:0(69.56.2.92):SA:1(13.1/5.0): 11.73458 4473
[EMAIL PROTECTED] [EMAIL PROTECTED]
What's_your_Car_Worth_at_Trade_In?
<[EMAIL PROTECTED]>
1128020771.29246-0.external.elih.org:3589
orig-external.elih.org112802076848729244:4473
Notice the SA:1(13.1/5.0) which shows that SA scanned the message and
scored it 13.1
Check qmail-scanner-queue.pl and look for:
#Array of virus scanners used must point to subroutines
my @scanner_array=("clamdscan_scanner","spamassassin");
This tells qmail-scanner to use ClamAV and SpamAssassin. What do the
headers of some messages say? Do any mention SA at all?
So I guess mail is definitely reachin the scanner but I dotn know where can I
specify that scanner pass on these mails to SA. Also I am unsure of the type of
flow that a mail goes through.
I cant upgrade qmail-scanner to 1.25 since we want to stick to these settings
for now; but I have version 1.20 which is good as well, right?
I dont know..there have been many improvements in newer versions, you
may want to upgrade. If you look at qmail-scanner-queue.pl you will see
the exact configure settings that were used to build it. You can then
use these same settings to build the new version. Its quite easy actually..
-Jim
