RE: [SAtalk] local.cf syntax

2002-10-25 Thread dmarie-spamassasin
Posté par Damian Mendoza le 25/10. What if I wanted to block specific subject keywords that are not already defined as a spamassassin rule? >> you can specify your own rule ... that is what rox in SA. its user configurable! Would I add the rule to the local.cf file or spamassassin.cf file and

re : [SAtalk] local.cf syntax

2002-10-24 Thread dmarie-spamassasin
Posté par Damian Mendoza le 25/10. Hi, I want to block all messages with VIAGRA, FREE, SEX, PORN, etc in the subject of a message. I would set the score to a very high value. How would I define the syntax in the local.cf file? Would the score also be in the local.cf file? >> for sitewide impl

re : [SAtalk] run SA/procmail in background

2002-10-24 Thread dmarie-spamassasin
After rebooting (~100 new messages) using my box is no fun at all due to a lot of spamassassin processes running. Except for using spamd what can I do against this? I'm running SA on Debian woody with exim as MTA and fetchmail. Running the MTA nicely (and therefore all of its childs including proc

re : [SAtalk] Permanent whitelist--newbie Q\'s

2002-10-24 Thread dmarie-spamassasin
>What I am unclear on is what the name of this .cf file should >be "60_whitelist.cf"? >"65_whitelist.cf"? "mypermanentwhitelist.cf"? >I also do not understand whether sa adds the names in my >/etc/mail/spamassassin/ cf file to those >in /usr/share/spamasassin/ or susbtitutes >them. i use onl

re : Re: [SAtalk] spamd uses a lot of CPU

2002-10-23 Thread dmarie-spamassasin
>Scott Lambert wrote: >Seperate the two functions. Run spamd on a dedicated box with lots >of CPU and memory. Disk is not terribly important. Just add -d >spamd.box.domain to you spamc invocation on the mail server. im currently already running them as 2 separate functions but on the same mac

[SAtalk] spamd uses a lot of CPU

2002-10-22 Thread dmarie-spamassasin
hi list i am maintaining a site-wide setup of spamassassin. we dont have any problems with the CPU load when there are not much mails received by the server. however, once the mails received go higher than 50 at one time, the CPU load shoots up to 90% or higher. and when this happens the mail