He noticed that some messages, including spam, were not being scanned by Spamassassin and were generating a log entry like this:
Code: Select all
qmail-scanner-queue.pl: qmail-scanner: Clear:RC:0(sending-ip-address):SA:0(?/?): (message details....)
After going round in circles and looking at logs and going absolutely nuts, I discovered that the messages in question all had attachments or inline images. Not huge ones though. Just typical attachments - a pdf here, a jpeg there.
For example, one message was just 2.3Mb in size including some inline images.
Looking at the qmail-scanner-queue.pl, I noticed two things:
1) At the top, in the configure detail line, it shows: --sa-maxsize 1024000 --- This is 1Mb.
2) In the bowels of the file, the following code can be found:
Code: Select all
# st: I have returned to my own way to set the (1.25st) my $spamc_binary='/usr/bin/spamc'; my $sa_timeout='120'; my $sa_maxsize='1024000'; [snip snip] $spamc_binary.=" -t $sa_timeout" if ($sa_timeout ne ""); $spamc_binary.=" -s $sa_maxsize" if ($sa_maxsize ne "");
Set the maximum message size which will be sent to spamd -- any bigger than this threshold and the message will be returned unprocessed (default: 250 KB). If spamc gets handed a message bigger than this, it won't be passed to spamd.
The size is specified in bytes, as a positive integer greater than 0. For example, -s 250000.
Editing my $sa_maxsize='1024000'; to add another 0 in the live qmail-scannerqueue.pl instantly caused the messages that were not being scanned to be scanned.
from looking at /usr/share/qmail-scanner/qmail-scanner-queue.template, it looked like you could change the value of this through the configuration file. So I added
SA_MAXSIZE="10240000" (i.e. an extra 0) to qmail-scanner.ini, did a qmail-scanner-reconfigure and
errr...EDIT!...I thought it worked! But it doesn't!
Does anybody have any suggestions about how to get this to stick through a reinstall or a reconfigure?