Hello Gary,
Just a quick reply - I looked in /var/log/mail.log and spotted the
following line that came up loads in the log file:
Jan 31 17:48:12 destiny spamd[15602]: prefork: syswrite(6) failed,
retrying... at /usr/share/perl5/Mail/SpamAssassin/SpamdForkScaling.pm line
554.
This might be my p
Hello Gary,
Just a quick reply - I looked in /var/log/mail.log and spotted the
following line that came up loads in the log file:
Jan 31 17:48:12 destiny spamd[15602]: prefork: syswrite(6) failed,
retrying... at /usr/share/perl5/Mail/SpamAssassin/SpamdForkScaling.pm line
554.
This might be my pr
How to flush the database?
But I don't see how they can cause the problem - why they scan the
email in a few seconds, then jump up into the regions of 300 seconds?
A Bayes DB expire can take up to 10 minutes to complete, depending on
your system and how big your bayes DB is.
However, this shou
Hello,
Have done that, spamassassin keep letting in a lot of spam, also I keep
getting multipile emails from some people.
Any ideas of what I can do now?
Thanks!
Regards - Piers
Matt Kettler wrote:
Piers Kittel wrote:
Loren,
How to flush the database?
But I don't see how they can cause
Piers Kittel wrote:
> Loren,
>
> How to flush the database?
>
> But I don't see how they can cause the problem - why they scan the
> email in a few seconds, then jump up into the regions of 300 seconds?
A Bayes DB expire can take up to 10 minutes to complete, depending on
your system and how big y
Loren,
How to flush the database?
But I don't see how they can cause the problem - why they scan the email
in a few seconds, then jump up into the regions of 300 seconds?
Also, spamassassin is already set to run a maximum of 5 childs. Also,
swap hasn't been used at all since last server res
Possibly SA is trying to do a Bayes or Awl expire while processing a
message, and that can take considerable time, especially if your Bayes or
Awl databases have gotten very large.
Possibly you are running too many children for the ram you have, and have
gone into thrashing.
Loren
Hello all,
Recently, found a vast amount of spam was coming in, that spamassassin
was supposed to kill, so had a look in the logs and found stuff like:
2006-01-28 06:52:20 1F2jwZ-0008Qr-Up SA: Debug: SAEximRunCond expand
returned: '1'
2006-01-28 06:52:20 1F2jwZ-0008Qr-Up SA: Debug: check succ
