> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Gary V > Sent: Thursday, August 03, 2006 12:45 PM > To: amavis-user@lists.sourceforge.net > Subject: Re: [AMaViS-user] sa-update (sa v 3.1.4) > > MrC wrote: > > >> > There might be different behaviors depending upon whether > >> --updatedir > >> > was used with sa-update, and where you perl installation > is. In my > >> > case, perl is in /usr/local, SpamAssassin default rules are in > >> > /usr/local/spamassassin, > >> > >> or is that /usr/local/share/spamassassin? I'm not sure SA > would look > >> in /usr/local/spamassassin unless told to do so. > >> > > > Arg, yes, my typo: /usr/local/share/spamassassin it is. > > > MrC > > Still testing LOCAL_STATE_DIR => '/var/lib', > > I upgraded from Debian 3.1.3 to the CPAN 3.1.4 and prior to > running sa-update, this version is using default rules in > /usr/local/share/spamassassin where the Debian version was > using /usr/share/spamassassin for default rules. After > sa-update it's using > /var/lib/spamassassin/3.001004/updates_spamassassin_org as expected. > The point being (at least with current versions of SA) the > code change does not seem to be a problem with older versions > of SA, nor when SA is upgraded. BTW mixing SA installation > methods like this is usually a really bad idea unless you > understand how your system will react and you know to fix > your system afterwards (if necessary). This particular test > system is no stranger to this kind of abuse. (8-} > > I would guess the only people this may have an adverse effect > on would be those who place custom rule sets in the default > rules dir and also use 'sa-update'. They shouldn't be doing > that at any rate, I believe custom rules go in the site rules dir. >
Yes, agreed. When Mark posted about Mail::SpamAssassin not finding the updates, and I knew my installation did, I wondered why, and discovered it was a side affect of having my updated rules installed into a subdir of the default rules location. Since I manually update my server software (i.e. no rpm, apt, etc.), I'm not really too concerned about where the updated rules end up, as long as they are working correctly. It looks like the patch going into SA 3.1.5 explains the details a little better, and looks in an additional location for local_state_dir. http://issues.apache.org/SpamAssassin/attachment.cgi?id=3624 MrC ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
