spamassassin-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karsten Br├Ąckelmann <guent...@rudersport.de>
Subject Re: can I roll back to an earlier version of updates
Date Mon, 01 Mar 2010 12:05:10 GMT
On Mon, 2010-03-01 at 06:45 -0500, Lee Dilkie wrote:
> Karsten Br├Ąckelmann wrote:

> > Anyway, what comes to mind: Did you run sa-update after the upgrade to
> > 3.3.0 at all? If not, did you install the rules tarball alongside SA?
> 
> I was originally running the 3.3 rules and that was fine, and as far as
> I know, I did even run sa-upgrade (can't tell you if it upgraded the
> rules over the base ones) but it's the latest sa-update that pulled in
> newer rules that didn't link. And it's my monkeying around, deleting
> rules directories, that has left me without rules from updates
> spamassassin_org. And boy! do they block a lot of spam or what! ;)
> 
> > How did you upgrade? Any chance both versions ended up living on your
> > system?
> >
> > Running 3.3.0 with a broken sa-update for whatever reason, can be cured
> > by removing the entire update dir, and installing the plain, stock 3.3.0
> > rules tarball, if not already done.
> 
> I'm on freebsd, I'm going to try and find out where that's stored, it's
> likely in the ports tree somewhere.

man spamassassin

See the section Configuration Files. The first path mentioned for
Default Configuration Data should be the sa-update one. SA version is
embedded in that path, inside /var/lib here, IIRC /var/db or something
on FreeBSD.

The last one in that block of paths should be where SA expects the stock
rules. The first existing one from that list wins, anything else will be
ignored.

spamassassin -D  can help in identifying bad rule sets being picked up,
and where SA ultimately looks for the cf files.


> Is there any way that I can force the system to download the ruleset so
> I can comment out the offending lines and carry on? (I'd at least like
> to see what they are, and why it doesn't parse, maybe it's something in
> my config).

Drop the bad update first, and revert to stock. Re-install it from
ports, if need be.


-- 
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0;
}}}


Mime
View raw message