On 30 May 2019, at 14:20, David Jones wrote:
On 5/30/19 8:10 AM, Kevin A. McGrail wrote:
I would check your spamd logs and see the time each message scan is
taking. My servers can keep tons of spamd running at 100% just
because
of constant mail.
In other words, just having 5 processes at full load really doesn't
mean
much.
On Thu, May 30, 2019, 09:06 Larry Nedry <spamassas...@bluestreak.net
<mailto:spamassas...@bluestreak.net>> wrote:
On 5/29/19 7:32 AM, Karsten Bräckelmann wrote:
> That's a non-scoring sub-rule, setting its score to 0 has no
effect.
> Redefining the rule to disable it is the way to go:
>
> meta __STYLE_GIBBERISH_1 0
FWIW, I've added this to local.cf <http://local.cf>, recompiled,
and
restarted spamd but
am still seeing CPUs hanging at 100%.
Larry
I am using MailScanner which launches spamassassin on batches of
emails
and the past couple of weeks I have been getting SA timeouts and being
killed by MailScanner. I have never found a way to troubleshoot this
as
I can't reproduce it consistently. I am using KAM.cf which has the:
meta __STYLE_GIBBERISH_1 0
line but does that need to be:
score __STYLE_GIBBERISH_1 0
to completely disable it?
No. The 'meta' line overrides the 'rawbody' line in the default ruleset
so you don't need anything else.
