Some scores have negative values. Some of the negative values are
big enough to make 30 into a negative score.
This is a discussion that comes up quite often. And it's been decided
every time that no change should be made.
On another paw, more memory is generally a good way to speed up the
spamassassin operation. A good DNS setup is also required so that you
do not get delays in DNS lookups. Do not select DNS tests for sites
that no longer exist. That is a major slow down.
Now, when you complain about speeds how about some numbers. What is
the processor speed, what is the amount of memory, what other things
run on the computer, how long is "spamassassin --lint" taking, how
long is a typical message processing take, and so forth. Give us
something to work with. THen we can tell you what is wrong. Of
particular interest are non-stock things you are doing. Did you add
additional DNS tests, for example?
{^_^}
----- Original Message -----
From: "Stefan Ewert" <[EMAIL PROTECTED]>
To: <users@spamassassin.apache.org>
Sent: 2005 June, 13, Monday 08:06
Subject: Boost up Spamassassin option
Hi,
does anyone know about a option which speeds up spamassassin extremly:
order the tests: fastest first, getting slower , slowest is the last test in
the list (dns perhaps, razor, pyzor, dcc).
and now: stop testing the mail, as soon as spamscore is greater than needed
to
be marked as a spam mail.
i dont want to know if this mail has got 30 points, im just interested in a
decision between spam and not spam.
regards s.
--
"UNIX ist benutzerfreundlich - es ist nur etwas wählerisch..." (Walter
Misar)
