Worked.
I am now scanning all the mail, the load average on the system is
load averages: 0.83, 1.00, 0.98
spamd -u nobody -d -L
and removed the spam.lock. Procmail is at about 60 processes per second
but it seems to be clearing them quickly. Most email gets scanned in 0 or
1 second. I have seen some at 2 seconds. I have contacted mail-abuse and
I am going to get a secondary of their zone files and run it locally for
the DNS based lookup, and I think that it will be ok.
brad
On 17 Jan 2002, Craig Hughes wrote:
> On Thu, 2002-01-17 at 12:29, brad wrote:
>
> :0fw:spam.lock
> | spamc -f
>
> :0e
> {
> EXITCODE=$?
> }
>
> and no there are not hundreds of spamc processes that I noticed. I did
>
> Yeah, as I thought. You're using a (probably global) lockfile on this
> recipe, so procmail is waiting for the previous spamc to finish before
> it starts the next one. Try this instead:
>
> :0fw
> | spamc -f
>
> :0e
> {
> EXITCODE=$?
> }
>
> That'll remove the unneccessary locking, and should mean you have fewer
> procmails waiting around for the other ones to finish.
>
> C
>
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
