On Friday 22 April 2011 4:44:57 pm Karsten
Bräckelmann wrote:
> On Fri, 2011-04-22 at 16:19 -0400, Dimitri
Yioulos wrote:
> > Over the past few days, I've had some spam
> > leaking through what has been an old, but
> > reliable system (consisting of the latest
> > Sendmail, MailScanner, clamav, MailWatch, and
> > an older Spamassassin, all running on a
> > CentOS box). Up to this point, most spam was
> > easily tagged and dealt with. But, I figured
> > I'd upgrade to the latest SA, thereby using
> > the most recent rules. Good in theory, bad
> > in practice, because it messed up Bayes.
> > Regardless of whether I tried to do it
> > manually, or via MailWatch, when I did an
> > sa-learn, I got the following:
> >
> > SA Learn: config: configuration file
> > "/etc/mail/spamassassin/20_advance_fee.cf"
> > requires version 3.003001
>
> ^^^^^^^^^^^^^^^^^^^^^^^
> That is NOT the place for the SA stock
> rule-set, but your local site config only.
>
> Seems, you did not mess up your Bayes DB, but
> the installation of the new SA version 3.3.1.
> The next line clearly shows the 'sa-learn' you
> are running is an older version, 3.2.5.
>
> > of SpamAssassin, but this is code version
> > 3.002005. Maybe you need to use the -C
> > switch, or remove the old config files?
> > Skipping this file at
> > /usr/lib/perl5/vendor_perl/5.8.0/Mail/SpamAss
> >assin/Conf/Parser.pm line 372.
> >
> > That's just a snippet; every rule does the
> > same. So, I figured I'd role back to the
> > previous version of SA. Trying sa-learn
> > again, I now get the following:
> >
> > SA Learn: config: configuration file
> > "/etc/mail/spamassassin/20_advance_fee.cf"
> > requires version 3.002005 of SpamAssassin,
> > but this is code version 3.002004. Maybe you
> > need to use the -C switch, or remove the old
> > config files? Skipping this file at
> > /usr/lib/perl5/vendor_perl/5.8.0/Mail/SpamAss
> >assin/Conf/Parser.pm line 372.
>
> Similar picture. Your "rolling back" to SA
> 3.2.5 severely borked your installation
> somehow, again, putting the stock rule-set in
> your site config.
>
> Strangely enough, your 'sa-learn' this time is
> 3.2.4 (!) though.
>
> > In other words, Bayes (or something) seems to
> > be looking at a previous configuration, or
> > whatever.
>
> Or whatever. ;)
>
> (a) Your installation is severely broken, with
> stock rule-set ending up in your site-config.
>
> (b) For some strange reason, you manage to
> always run an older sa-learn executable, than
> would have been expected.
>
> How exactly did you install 3.3.1? How exactly
> did you revert?
>
>
> --
> 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; }}}
Hi, Karsten.
Also glad you're aboard.
Don't know how I managed to mangle my SA
configuration, but how you all will help me
untangle. I used the Dag repo for version 3.2.5,
but ran rpmbuild against the SA tarball for 3.3.1
(I can almost see you grimacing). Previous
version was removed with rpm -e. It's possible
the I did an rpm -Uvh to upgrade old to new.
(excuse time - we moved our 75-person office this
past week, and I managed the project. Note to
self - don't mess around with stuff when dog
tired).
Dimitri
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
