On 12/3/2012 3:03 PM, Henrik K wrote:
Two, I'm trying a system that also truncates messages mid-message at
the threshold to scan them anyway.
The second idea has been pretty controversial but I think the first
one is a neat idea.
Why is it controversial? Amavisd-new 2.6.3 had this feature since 2009, so
it's used probably very widely - even without users knowing it. I've never
seen any ill effects.
There have been emails on list in the past few weeks. I believe AXB is
anti the concept. I have no opinion yet which is why I am testing.
This might be something neat to add to spamd/spamc natively where
there is a load average multiplier concept. Thoughts?
Load average is quite silly measurement. The maximum depends on the number
of cpu cores/threads. Also this kind of limiting makes sense only on a
pre-queue filter in which case such "throttles" should be applied way before
anything gets to SA.
I'm simply trying to maximize resources and right now, the reason SA
doesn't scan infinitely is because large messages take more time to
process. Using Load Average, which I agree is a bit amorphous, is a
quick gauge of resources that are available and allows me to
automatically raise and lower the size limit for spamc/d in a way that
is not controversial such as the truncation method.
Regards,
KAM
