Re: sa-update damages existing SA installation

2008-12-19 Thread mouss
Gene Heskett a écrit : On Thursday 18 December 2008, Kai Schaetzl wrote: Gene Heskett wrote on Thu, 18 Dec 2008 15:13:28 -0500: Following the above tut, step 2 fails as root owns the /etc/mail tree, and the user running SA has no perms. What should the owner/group actually be for that? I

Re: sa-update damages existing SA installation

2008-12-19 Thread Marcin Krol
Daryl C. W. O'Shea wrote: do it all at once. See my SARE sa-update page for details: http://daryl.dostech.ca/sa-update/sare/sare-sa-update-howto.txt Are SARE rules still being updated a bit at least / are they still working? The home page bears warning IMPORTANT: Due to Ninjas being busy

Adding SARE rules

2008-12-19 Thread Marcin Krol
Hello everyone, 1. First of all, as SARE rules don't seem to be updated anymore, does it still make sense to add them? 2. Assuming that it does, which SARE rules do you use? Or should I just add them all? Regards, Marcin

Re: sa-update damages existing SA installation

2008-12-19 Thread Gene Heskett
On Friday 19 December 2008, mouss wrote: Gene Heskett a écrit : On Thursday 18 December 2008, Kai Schaetzl wrote: Gene Heskett wrote on Thu, 18 Dec 2008 15:13:28 -0500: Following the above tut, step 2 fails as root owns the /etc/mail tree, and the user running SA has no perms. What should the

Re: sa-update damages existing SA installation

2008-12-19 Thread Kai Schaetzl
Gene Heskett wrote on Fri, 19 Dec 2008 09:04:52 -0500: 2. And what do I do to my /etc/init.d/spamassassin script so it will use the newly fetched .cf files instead of the ones in /usr/share/spamassassin? is that spamd or what? Reload it. Kai -- Kai Schätzl, Berlin, Germany Get your web at

Re: sa-update damages existing SA installation

2008-12-19 Thread Gene Heskett
On Friday 19 December 2008, Kai Schaetzl wrote: Gene Heskett wrote on Fri, 19 Dec 2008 09:04:52 -0500: 2. And what do I do to my /etc/init.d/spamassassin script so it will use the newly fetched .cf files instead of the ones in /usr/share/spamassassin? is that spamd or what? Reload it. Kai

RE: Adding SARE rules

2008-12-19 Thread Chris Santerre
As of right now they are not being updated. But still being used, even by myself. --Chris -Original Message- From: Marcin Krol [mailto:mrk...@gmail.com] Sent: 2008-12-19 06:35 To: users@spamassassin.apache.org Subject: Adding SARE rules Hello everyone, 1. First of all, as

Re: sa-update damages existing SA installation

2008-12-19 Thread Kai Schaetzl
Gene Heskett wrote on Fri, 19 Dec 2008 09:43:13 -0500: Anything else, like setting up a weekly update run in that new users crontab? sure. I think most people do it daily. If you use sa-compile adds this to the script as well. Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive

RE: Adding SARE rules

2008-12-19 Thread Bowie Bailey
Marcin Krol wrote: 2. Assuming that it does, which SARE rules do you use? Or should I just add them all? Don't just blindly add them all. Not all of them are appropriate for everyone and some of them have different versions for different SA versions. Read the descriptions and see which ones

Re: iXhash issues

2008-12-19 Thread Karsten Bräckelmann
On Thu, 2008-12-18 at 15:07 +0100, Marcin Krol wrote: Hello everyone, Is it just me or iXhash all of a sudden causes problems? I got very high load and memory consumption on multiple spamd instances hanging there and just consuming CPU. When I turned iXhash off, the mailserver got back

Re: sa-update damages existing SA installation

2008-12-19 Thread Karsten Bräckelmann
On Fri, 2008-12-19 at 16:31 +0100, Kai Schaetzl wrote: Gene Heskett wrote on Fri, 19 Dec 2008 09:43:13 -0500: Anything else, like setting up a weekly update run in that new users crontab? sure. I think most people do it daily. If you use sa-compile adds this to the script as well.

Re: Learning SPAM

2008-12-19 Thread Luis Croker
Hi... I have fixed the problem... I dont know if this is the best method...I have copied the following files, from the old server to the new server... mailgw# pwd /var/amavis/.spamassassin mailgw# ls -al total 25298 drwx-- 2 vscan vscan 512 Dec 19 11:31 .

Re: sa-update damages existing SA installation

2008-12-19 Thread mouss
Gene Heskett a écrit : Stumbling around in the dark, I created that user, and chowned the /var/lib/spamassassin directory to that user:mail, made saupdate a member of group mail. Why? if you do random mixing of owners and groups, you'll end up making your system more vulnerable than it

Re: Adding SARE rules

2008-12-19 Thread mouss
Marcin Krol a écrit : Hello everyone, 1. First of all, as SARE rules don't seem to be updated anymore, does it still make sense to add them? 2. Assuming that it does, which SARE rules do you use? Or should I just add them all? no, don't add them all. you need to read their description

Re: sa-update damages existing SA installation

2008-12-19 Thread Gene Heskett
On Friday 19 December 2008, Kai Schaetzl wrote: Gene Heskett wrote on Fri, 19 Dec 2008 09:43:13 -0500: Anything else, like setting up a weekly update run in that new users crontab? sure. I think most people do it daily. If you use sa-compile adds this to the script as well. Kai I didn't want

Re: sa-update damages existing SA installation

2008-12-19 Thread Gene Heskett
On Friday 19 December 2008, mouss wrote: Gene Heskett a écrit : Stumbling around in the dark, I created that user, and chowned the /var/lib/spamassassin directory to that user:mail, made saupdate a member of group mail. Why? if you do random mixing of owners and groups, you'll end up making

Re: sa-update damages existing SA installation

2008-12-19 Thread mouss
Gene Heskett a écrit : OTOH, if I run it as root, then the clients have no perms. Tell me a way around that please. I run it as root, like almost everybody. the clients only need read access to the directory, which should be the case by default, unless you played with the root umask.

Re: sa-update damages existing SA installation

2008-12-19 Thread Gene Heskett
On Friday 19 December 2008, mouss wrote: Gene Heskett a écrit : OTOH, if I run it as root, then the clients have no perms. Tell me a way around that please. I run it as root, like almost everybody. the clients only need read access to the directory, which should be the case by default, unless

Re: sa-update damages existing SA installation

2008-12-19 Thread Daryl C. W. O'Shea
On 19/12/2008 5:40 AM, Marcin Krol wrote: Daryl C. W. O'Shea wrote: do it all at once. See my SARE sa-update page for details: http://daryl.dostech.ca/sa-update/sare/sare-sa-update-howto.txt Are SARE rules still being updated a bit at least / are they still working? The only one really