i got one mail today that tricker this spamassassin 2>&1 -D -t mail | less
stops when rule eval begins, and from there control c cant stop scanning again and we use 100% cpu time :/ how do i find with rule, or how to debug it future ? am i the only one that have seen long scan times on mails ? using 3.2.5 here -- Benny Pedersen Need more webspace ? http://www.servage.net/?coupon=cust37098
