Spamassassin not working after 4.53

[Glenn Steen]

On 03/05/06, Devon Harding <devonharding at gmail.com> wrote:
> Here are my sa-update results:
>
> [root at mars dcc-1.3.31]# sa-update
> error: can't verify SHA1 signature
> channel: SHA1 verification failed, channel failed
>
> hmm..There are rules in /usr/share/spamassassin, but nothing in
> /var/lib/spamassassin/3.001001
>
> [root at mars dcc-1.3.31]# l /var/lib/spamassassin/3.001001/
> total 8.0K
> drwxr-xr-x 2 root root 4.0K May  2 04:14 updates_spamassassin_org
> drwxr-xr-x 2 root root 4.0K May  2 04:14 updates_spamassassin_org.tmp
> [root at mars dcc-1.3.31]# l
> /var/lib/spamassassin/3.001001/updates_spamassassin_org
> total 0
> [root at mars dcc-1.3.31]# l
> /var/lib/spamassassin/3.001001/updates_spamassassin_org.tmp/
> total 4.0K
> -rw-r--r-- 1 root root 98 May  3 09:11 MIRRORED.BY
>
> How do I correct this?

Someone will definitely correct me if I'm wrong, but (re-)moving the
directory somewhere else (that SA will not try to find it) would
probably make it fall abck to /usr/share/spamassassin.

I'm sure Adri (or someone else) will have a handle on your SHA1 error
there... You saw Rogers resolution to his problem (FW of port 8090
preventing it from retreiving anything)?
I just tested running sa-update on a machine with port 8090 blocked,
and this is exactly the error that you get... after a longish time you
get:
-----
[root at apmx05 ~]# sa-update
sa-update: importing default keyring to
'/etc/mail/spamassassin//sa-update-keys'...
http: request failed: 500 Can't connect to
buildbot.spamassassin.org.nyud.net:8090 (connect: timeout): 500 Can't
connect to buildbot.spamassassin.org.nyud.net:8090 (connect: timeout)
error: channel updates.spamassassin.org has no working mirrors
channel: could not find working mirror, channel failed
-----
and then the /var/lib/spamassassin/<version> directory is created
_without the "old" rules!

This is bad only if you have never successfully run sa-update, since
otherwise you'll have your "old rules" in place, but when it happens
the first time, you neither get the encryption keys (it seems to me),
nor any working rules.... Bah.
Either fall back to the "default" rules by deleting the dir, or make
darned sure the first run succeeds. You might need delete the
/etc/mail/spamassassin/sa-update-keys directory and the
/var/lib/spamassassin/3.001001 for that to actually work (after
opening port 8090).

HtH
--
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se