[Mimedefang] CPU load problem

[Andy (An H. Nguyen)]

I only have a couple small rulesets and have tried turned it off as well as 
turning off AWL and Bayes.
Still having high cpu.... and still seeing lots of SpamAssassin scans on 
"md-mx-ctrl busyslaves"


Is it because of Mimdefang filter?
Can I call $Sender from filter_end?

        if ($hits >= $SpamScore) {
                my $recip;
                foreach $recip (@Recipients) {
                delete_recipient($recip);
                }
                add_recipient('outmail at my.edu');
                action_change_header("Subject", "[[JUNK]][[+SPAM]] 
$Subject");
                if ($Sender =~ m/my\.edu/i) {
                 add_recipient( $Sender );    }
                }


--------------------------------------------------
From: "David F. Skoll" <dfs at roaringpenguin.com>
Sent: Tuesday, October 14, 2008 5:40 AM
To: <mimedefang at lists.roaringpenguin.com>
Subject: Re: [Mimedefang] CPU load problem

> Andy (An H. Nguyen) wrote:
>
>> 0 B 14609 (last=scan) (2: > Running SpamAssassin m9E0955I017916)
>> 1 B 14610 (last=scan) (2: > Running SpamAssassin m9E093AR017881)
>> 2 B 14611 (last=scan) (2: > Running SpamAssassin m9E093Dg017888)
>> 3 B 14612 (last=scan) (2: > Running SpamAssassin m9E093OD017904)
>> 4 B 14637 (last=scan) (2: > Running SpamAssassin m9E093fe017887)
>> 5 B 14639 (last=scan) (2: > Running SpamAssassin m9E092mV017878)
>> 6 B 14642 (last=scan) (2: > Running SpamAssassin m9E094ZB017909)
>> 7 B 14644 (last=scan) (2: > Running SpamAssassin m9E0938g017906)
>> 9 B 14648 (last=scan) (2: > Running SpamAssassin m9E093To017905)
>> 10 B 14651 (last=scan) (2: > Running SpamAssassin m9E093c1017907)
>> 11 B 14653 (last=scan) (2: > Running SpamAssassin m9E093aB017908)
>
>> Does this mean that mimedefang-multiplexor eats all the CPU load because 
>> of spamassassin?
>
> Yes, that's what it means.
>
>> I'm running the latest spamassassin version, I will try local dns cache 
>> to see if it helps.
>
> It will not.  Do you have any extra SpamAssassin rulesets?  Some
> rulesets are not very well written and use tons of CPU time.  I recommend
> removing all rulesets except those actually shipped with SpamAssassin
> and then enabling them one at a time until you find the culprit.
>
> Regards,
>
> David.
> _______________________________________________
> NOTE: If there is a disclaimer or other legal boilerplate in the above
> message, it is NULL AND VOID.  You may ignore it.
>
> Visit http://www.mimedefang.org and http://www.roaringpenguin.com
> MIMEDefang mailing list MIMEDefang at lists.roaringpenguin.com
> http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
>