On 11/01/2017, 09:52, "Matus UHLAR - fantomas" <uh...@fantomas.sk> wrote:
>>>> On 10/01/2017, 23:01, "Reindl Harald" <h.rei...@thelounge.net> wrote: >>>>> you setup a new server with 3.3.2 in 2017? >>>>> >>>>> current is 3.4.1 and i know people running it on Debian for more >>>>>than a >>>>> year - sorry but why are you doing that? > >>>Am 10.01.2017 um 23:09 schrieb Andrea: >>>> You¹re right. >>>> It seems that something was left over from the previous debian >>>>release: >>>> >>>> root@srv1:~# whereis spamassassin >>>> spamassassin: /usr/bin/spamassassin /etc/spamassassin >>>> /usr/local/bin/spamassassin /usr/share/spamassassin >>>> /usr/share/man/man1/spamassassin.1p.gz >>>> >>>> >>>> root@srv1:~# /usr/local/bin/spamassassin -V >>>> SpamAssassin version 3.3.2 >>>> running on Perl version 5.20.2 >>>> >>>> root@srv1:~# /usr/bin/spamassassin -V >>>> SpamAssassin version 3.4.0 >>>> running on Perl version 5.20.2 > >>>that sounds bad - package managers are supposed to clean leave files and >>>report package versions > >they do. /usr/local/bin/spamassassin is NOT from debian package. debian >doesn't put package files to /usr/local/bin > >I wonder why was there 3.3.2 in /usr/local/ since the wheezy version was >3.3.2 too. > >>>however - did you run "sa-update" after your setup was finished because >>>otherwise you are *far away* from a proper setup and recent rules > >On 10.01.17 23:31, Andrea wrote: >>I did run sa-update..but now it seems that the concurrent versions issue >>affects all sa binaries (sa-learn, sa-update, etc). >>I wonder what went wrong since I followed the Debian upgrade procedures >>and I _never_ installed anything that wasn’t coming in a package from the >>official repositories. > >seems you did have locally installes SA though (as noted above - anything >in >/usr/local is NOT from debian distribution) - did you fix your problem by >removing it? > >if not, did you check configuration files in /etc/spamassassin/ ? >which spamassassin do you call from master.cf? >It's possible that locally installed uses files in other directories which >may have caused your problem Fixing the binary paths actually did resolve the issue. I am now back at “acceptable” detection levels. I’m still trying to figure out where did the outdated packages come from though
