SpamAssassin is a memory pig even when you first start it up.  As for it 
being in Perl ... well, processing text in a complex way is Perl's 
strength, and that's essentially what SpamAssassin is all about.  You 
could probably write a similar (and faster) engine using C and libpcre, 
but you wouldn't be able to plug stuff into it as easily as you can with 
the current perl implementation.  
   
 I keep the memory leaks at bay by restarting it every night after running 
sa-update.  It's not as if it's citserver where everyone gets forcibly 
logged off if you restart it.  :)  
  

Reply via email to