[SAtalk] Tracking down slow parts of SA...

2003-10-28 Thread Henrik Schmiediche
Hello, I have SA 2.60 deployed. I am trying to track down why --- occasionally --- scanning a message using SA takes a very long time. Currently most spam is scanned within 2.5 seconds (median) on a 900 MHz Sun system. I have the following time limits in local.cf: rbl_timeout 10

RE: [SAtalk] SpamAssassin 2.60 rc4 released

2003-09-12 Thread Henrik Schmiediche
Hello, Has something PATH wise changed on rc4? I installed rc4 and suddenly SA cannot find dccproc and pyzor which are installed in my mail/spam/virus bin directory. Creating link(s) in /usr/local/bin to dccproc pyzor fixed the problem and SA can then find the programs, but I do not

[SAtalk] Documentation: autolearn cutoff values in 2.60-rc3

2003-08-29 Thread Henrik Schmiediche
Hello, The documentation for 2.60-rc3 claims the bayes auto learn cutoff values are -2 15. I think they have been changed to 0.1 and 12. Is that correct? Sincerely, - Henrik --- This sf.net email is sponsored by:ThinkGeek

RE: [SAtalk] Re: SpamAssassin 2.60 rc3 released

2003-08-29 Thread Henrik Schmiediche
I would like to second the notion that having to specify SYSCONFDIR is going to cause sys-admins problems that do not follow this list. I have no problem with the idea in principle; I just think it needs to be well documented, preferable with a run-time-install check. The SYSCONFDIR issue was

RE: [SAtalk] OT- greylisting - opinions from the SA community?

2003-06-24 Thread Henrik Schmiediche
Hello, The way I understand greylisting it will have to be implemented at the MTA level, so I am not sure it could be implemented in spamassassin. Nonetheless, for all the initial negative reaction in this forum, greylisting is a fantastic new proposal which will be implemented at many sites.