* Ralf Hildebrandt <[EMAIL PROTECTED]>: > I'm using spamassassin from within amavisd-new. Loggin shows that > amavis's SA-check is the most time-consuming step while processing an > email (>>80% of the total time needed). > > How can I run spamassassin against some mails to find out what part of > spamassassin (maybe some sort of external DNS query) takes how much > time? > > I was thinking of a sort of "profile" (subrouting x takes y seconds) > to find out where my particular installation of SA is "slow".
By trial and error I found out that the activation of bayes makes things unbearably slow. use_bayes 0 and all is well, use_bayes 1 bayes_auto_learn 1 bayes_learn_to_journal 1 bayes_path /home/sharedspam/.spamassassin/bayes bayes_file_mode 777 bayes_ignore_header ReSent-Date bayes_ignore_header ReSent-From bayes_ignore_header ReSent-Message-ID bayes_ignore_header ReSent-Subject bayes_ignore_header ReSent-To and things get slow. Why is that? -- _________________________________________________ Charité - Universitätsmedizin Berlin _________________________________________________ Ralf Hildebrandt i.A. des IT-Zentrum | Netzwerkdienste Stabsstelle des Klinikumsvorstandes Campus Mitte Schumannstr. 20/21 | D-10177 Berlin Tel. +49 30 450 570155 | Fax +49 30 450 570916 [EMAIL PROTECTED] http://www.charite.de
