Charlie Clark wrote:
Am 09.11.2006 um 02:10 schrieb Daryl C. W. O'Shea:
Charlie Clark wrote:
Looks like I'm on top of the resources problem but I am getting "421
delivery errors" even though the e-mails are coming through. This
looks very similar to bug 3828 (which is Spamassassin + Exim). Except
this bug should have been closed a long time ago.
Without looking at the bug, it sounds like you're saying that Exim
temp fails messages when a filter (SA) isn't available to filter the
message in time. If that's the case it's sensible for that to happen.
Indeed it is. I just don't understand why it is happening on this
machine which has a very low load.
If your one and only child is busy doing an expire it can't scan
messages too.
The strange thing is these errors never occurred before last week and
having just upgraded to 3.1.7 I would hope to have a system including
all relevant bug fixes.
Of course, as Theo said it might simply be easier to stop using spamd
and just call spamassassin but it might also be helpful to track down
the problem. Should I jump on the back of the old bug or make a new
submission?
Have you actually looked into making sure that you're not experiencing
an expiry issue (like the expiry being times out and never completed)
like Theo inferred you do off the bat?
No, and I'll admit to not really understanding exactly what you mean.
Where can I check and if necessary change this?
Disable bayes_auto_expire in your local.cf and run an expire manually
(and then set it up as a cron job) by running sa-learn --force-expire as
the user that SA normally runs as (if SA runs as more than one user, run
it for all the users it runs as). It's probably going to take a
considerable amount of time for it to run... let it finish, it will
eventually.
Daryl
