> > General advice: Post the error messages. Do a debug run. Post the
> > relevant parts of the debug info.
> >
> > Gene -- with your headstrong, infamous around here user setup, you
> > should first check exactly that -- users. Which one runs the cron job?
> > Which one do you sudo to? And which one imported the GPG key?
> 
> Thanks for the complement.  I have studied on trying to do it right for 
> almost 75 years now.

And yet you're doing it different than anyone else... ;)

> [25964] dbg: gpg: calling gpg
> [25964] dbg: gpg: gpg: Signature made Tue 18 Aug 2009 03:24:59 AM EDT using 
> DSA key ID 6C6191E3
> [25964] dbg: gpg: [GNUPG:] SIG_ID XMBVEC+9EnYV7uMWvdrn/1H/+Hw 2009-08-18 
> 1250580299
> [25964] dbg: gpg: [GNUPG:] GOODSIG DC85341F6C6191E3 Justin Mason Signing Key 
> (Code Signing Only) <signing...@jmason.org>
> [25964] dbg: gpg: gpg: Good signature from "Justin Mason Signing Key (Code 
> Signing Only) <signing...@jmason.org>"
> [25964] dbg: gpg: [GNUPG:] VALIDSIG 8D25B5E91DAF0F715F60B588DC85341F6C6191E3 
> 2009-08-18 1250580299 0 3 0 17 2 00 
> 8D25B5E91DAF0F715F60B588DC85341F6C6191E3
> [25964] dbg: gpg: [GNUPG:] TRUST_UNDEFINED
> [25964] dbg: gpg: gpg: WARNING: This key is not certified with a trusted 
> signature!
> [25964] dbg: gpg: gpg: There is no indication that the signature belongs to 
> the owner.
> [25964] dbg: gpg: Primary key fingerprint: 8D25 B5E9 1DAF 0F71 5F60 B588 DC85 
> 341F 6C61 91E3
> [25964] dbg: gpg: found signature made by key 
> 8D25B5E91DAF0F715F60B588DC85341F6C6191E3
> [25964] dbg: gpg: key id 6C6191E3 is not release trusted
                                       ^^^^^^^^^^^^^^^^^^^
You failed to provide the obligatory --gpgkey 6C6191E3 option.

> channel: GPG validation failed, channel failed
> 
> Obviously this is a trust setting, not a gpg failure as I assumed when I
> posted.  Which then begs the question of who is untrusted, me, or yerp.org?

Your sa-update run doesn't trust that key to sign releases. Please see
man sa-update [1] for general information about that option, and the
SOUGHT rule-set usage instructions [2] again, on how to use sa-update
with that channel.


[1] http://spamassassin.apache.org/full/3.2.x/doc/sa-update.html
[2] http://taint.org/2007/08/15/004348a.html

-- 
char *t="\10pse\0r\0dtu...@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; }}}

Reply via email to