From: "Stefan Ewert" <[EMAIL PROTECTED]>
> > 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.
> >
> sorry, i cant follow you, where can i read something about this topic?
A not uncommon problem I see on this list is people attempting to use
DNS test sites (Black List sites) that no longer exist. Then you get
a 10 second or so timeout on the DNS lookup attempts to that site.
> > 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?
> >
> first of all im not complaining, this is a misunderstanding. i just want
to
> help a little in the development of SA. im new in this list, so never
heard
> about this idea before ;)
> here are the facts: amd3000+, 512 MB, desktop pc, lint takes 5 secs, id
guess > a typical messages takes about 25 secs.
That sounds very much like your DNS based tests are failing. Try turning
off the DNS based tests and see what you get. Or run a test with a
message and the "spamassassin -D -t <message" format. The -D turns on
debug messages. And you can see where the long delays come from. It is
not from the normal rules or Bayes.
> im using the standard configuration file, so from my side i didnt add any
> other tests like dns. theres no nameserver running on my pc.
>
> just thougt, it would be very simple to stop testing at the right moment,
but
> it seems like i know to few about this filtering process.
>
> --
> MUM, CAN I GO OUT AND CODE TONIGHT?
In as much as I'm not your mother I can't say. Were you indeed my son
I'd be surprised if he was doing heavy coding. He's a mechanical
engineer working for a automaker.
{^_-}
