use Perl

• Shouldn't happen (Score:3, Informative)

  by Matts (1087)

  If it's happening it's a bug. Find out what mails caused it to slow down and submit a bug report and attach the mails in question.
  
  And turn off network checks. They can be very slow.
  
  And make sure you're using the latest release. There are often a number of timeout (network check related) fixes in each release. And we test the other rules extensively for performance issues.
  
  SpamAssassin is slow, but it really shouldn't kill your box.
  • Re:Shouldn't happen (Score:2, Informative)

    by Elian (119) on 2003.05.22 9:43 (#20411) Homepage Journal

    What kills SpamAssassin dead, or at least cripples my box, is when Vipul's Razor is off-line for some reason. That's the thing that makes the spamd processes stack up really badly. Not SpamAssassin's fault, definitely, though it does (or did) have issues not really timing out the way it should. (Which may well have been an issue with my box, for all I know)
    
    Procmail filtering the known-good (or known-bad--support@microsoft.com and big@boss.com) stuff so SpamAssassin has less to deal with is always a good thing too, as others have already pointed out.

    Reply to This

    Parent

    • Re:Shouldn't happen (Score:2)

      by Matts (1087)

      Ugh. De-install Razor. It bites.
      • Re:Shouldn't happen (Score:1)

        by Elian (119)

        I dunno--it seems to catch some of the stuff that'd otherwise make it through. I do admit I worry some about off-site and potentially un-checked content grading systems, but... I'm definitely up for alternatives, but I'm not sure pyzor's any better.
        • Re:Shouldn't happen (Score:2)

          by Matts (1087)

          Try DCC instead. It's a better implementation and overall a better idea.