Hello Technical, Thursday, July 14, 2005, 3:15:19 AM, you wrote:
TD> Hi TD> We are running Qmail Scanner 1.25 + Spamassassin 3.04 + Clamd 1.86.1 on TD> our dual 1.4Ghz P3 Linux mail server. We've been experiencing some TD> problems with the server taking a long time to scan messages (In most TD> cases they are taking between 60 and 80 seconds). I have the following TD> rulesets installed: TD> 70_sare_adult.cf 70_sare_unsub.cf init.pre TD> 70_sare_bayes_poison_nxm.cf 72_sare_bml_post25x.cf last-update TD> 70_sare_genlsubj0.cf 72_sare_redirect_post3.0.0.cf local.cf* TD> 70_sare_header0.cf 88_FVGT_subject.cf mr_wiggly.cf TD> 70_sare_html0.cf 90_FVGT.cf netcom.cf TD> 70_sare_obfu1.cf 99_sare_fraud_post25x.cf nov2rules.cf TD> 70_sare_oem.cf 99_sober.cf rolex.cf TD> 70_sare_ratware.cf DomainDigits1.cf surbl.cf TD> 70_sare_spoof.cf evilnumbers.cf weeds.cf If you use 70_sare_obfu1.cf, you should also be using 70_sare_obfu0.cf, or perhaps instead 70_sare_obfu.cf, which combines those two files into one. 70_sare_ratware.cf is empty/discontinued. Replace evilnumbers.cf with 70_sare_evilnum0.cf and possibly 70_sare_evilnum1.cf -- they're the current maintenance versions. mr_wiggly.cf is obsolete. Use 70_sare_specific.cf instead. Likewise, 70_sare_specific.cf should catch anything flagged by rolex.cf nov2rules.cf is nov 2003 and should probably be dropped. Any rules there of significant value have migrated to other rules files. Don't recognize the non-SARE rules files, but the ones you have shouldn't be causing the performance problem. Check your network connection. If SURBL tests are failing and timing out, that could cause the delays you're seeing. > spamassassin -D <message should give you output indicating what does and doesn't work. That might help you figure this out. Bob Menschel
