> On Wednesday 22 July 2009, Jari Fredriksson wrote: >>> I found the SOUGHT_FRAUD rules in jm's sandbox. Are >>> those the proper ones to use? Are the testing ones safe? >> >> Sandbox rules are not proper ones. >> >> Add >> >> sought.rules.yerp.org >> >> to your sa-update channels.txt file. >> >> My channels.txt >> >> updates.spamassassin.org >> sought.rules.yerp.org >> saupdates.openprotect.com >> >> channels.txt to the sa-update as a parameter. > > I've set mine up like that, but I'm having key problems. > As gene, I have repeatedly used wget to pull the keys, > and sa-update --IMPORT key \ --gpghomedir > /var/lib/spamassassin/keys, all without errors. > > The keyfile pubring is being touched. > > [g...@coyote ~]$ ls -l /var/lib/spamassassin/keys > total 28 > -rw------- 1 gene gene 4505 2009-07-22 20:16 pubring.gpg > -rw------- 1 gene mail 2783 2008-12-19 08:26 pubring.gpg~ > -rw------- 1 gene mail 0 2008-12-19 08:26 secring.gpg > -rw------- 1 gene mail 1200 2008-12-19 08:26 trustdb.gpg > > However when I run the sa-update, one key error remains: > ========================================================= > [g...@coyote ~]$ /usr/bin/sa-update --channelfile > ~/.spamassassin/channels.txt --gpghomedir > /var/lib/spamassassin/keys > error: GPG validation failed! > The update downloaded successfully, but the GPG signature > verification failed. > channel: GPG validation failed, channel failed > error: GPG validation failed! > The update downloaded successfully, but it was not signed > with a trusted GPG key. Instead, it was signed with the > following keys: > > BDE9DC10 > > Perhaps you need to import the channel's GPG key? For > example: > > wget http://spamassassin.apache.org/updates/GPG.KEY > sa-update --import GPG.KEY > > channel: GPG validation failed, channel failed > ============================================= > Obviously I'm dropping the ball, but where? >
Somewhere... I use --nogpg option, and do not bother my small ball. That's wrong, but I'm lazy.
