RobertH-2 wrote: > > > basically it all depends on the qmail-scanner config and it can be semi > complex and may not be correct in terms of if you reject over certain > score > or if you have other scanning functions happening before calling SA, like > clamav etc etc > > also, the message could be two big and bypassed, and that is controlled in > more than one place if i remember right. > > we disable clamav in qmail-scanner and use the clamav plugin, yet we also > reject at or above a certain score in the smtp session too. > > we do not use the newest qmail-scanner either, and the one we use is the > special patched one, ummm 1.25-st or something like that >
Well, the thing is that this is happening at a lower level than qmail-scanner--specifically, spamd. QMail-scanner takes the SpamAssassin score and then decides what to do with it. But the spamd logs show how certain messages are just skipped from evaluation altogether (as if there were no rules in SA at all) and given a clean score. They are not deleted or rejected; and that logic comes later, from Q-S anyway. With debugging on, spamd also reports a fair number of "sysread() not ready" messages, and lots of chatter about what's happening with child processes, but I take it this is all fairly normal. And these appear before and after messages are scanned, not during. -- View this message in context: http://www.nabble.com/Spamd-skipping-tests-tp21448225p21458936.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
