Mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j.@jmason.org (Justin Mason)
Subject Re: sa-update error wrong gpg key...
Date Fri, 25 Jan 2008 16:45:23 GMT

Kevin --  I have bad news. ;)  that's not coming from our channels,
it's the sare.sa-update.dostech.net channel I'd guess.

--j.

Kevin W. Gagel writes:
> ----- Original Message -----
> >hi Kevin -- what's the channel and command line?
> 
> Hi Justin,
> 
> Thanks for looking into this. I've copied and pasted everything below so
> that you have a complete picture.
> 
> The command line is (in a cronjob):
> sa-update --allowplugins --channelfile
> /etc/mail/spamassassin/sa-update-keys/sa-update-channels &&
> /etc/init.d/spamassassin restart
> 
> The channels are (all of them are failing, copied from the
> sa-update-channels file):
> 70_sare_adult.cf.sare.sa-update.dostech.net
> 70_sare_bayes_poison_nxm.cf.sare.sa-update.dostech.net
> 70_sare_evilnum0.cf.sare.sa-update.dostech.net
> 70_sare_evilnum1.cf.sare.sa-update.dostech.net
> 70_sare_genlsubj0.cf.sare.sa-update.dostech.net
> 70_sare_genlsubj2.cf.sare.sa-update.dostech.net
> 70_sare_header.cf.sare.sa-update.dostech.net
> 70_sare_html.cf.sare.sa-update.dostech.net
> 70_sare_obfu0.cf.sare.sa-update.dostech.net
> 70_sare_obfu1.cf.sare.sa-update.dostech.net
> 70_sare_oem.cf.sare.sa-update.dostech.net
> 70_sare_random.cf.sare.sa-update.dostech.net
> 70_sare_specific.cf.sare.sa-update.dostech.net
> 70_sare_spoof.cf.sare.sa-update.dostech.net
> 70_sare_stocks.cf.sare.sa-update.dostech.net
> 70_sare_unsub.cf.sare.sa-update.dostech.net
> 70_sare_uri0.cf.sare.sa-update.dostech.net
> 70_sare_whitelist.cf.sare.sa-update.dostech.net
> 70_sare_whitelist_rcvd.cf.sare.sa-update.dostech.net
> 70_sare_whitelist_spf.cf.sare.sa-update.dostech.net
> 72_sare_bml_post25x.cf.sare.sa-update.dostech.net
> 72_sare_redirect_post3.0.0.cf.sare.sa-update.dostech.net
> updates.spamassassin.org
> 
> This is what I receive in my inbox in the morning:
> 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: 
> 
> 856AA88A 
> 
> 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 
> 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: 
> 
> 856AA88A 
> 
> 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 
> 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: 
> 
> 856AA88A 
> 
> 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 
> 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: 
> 
> 856AA88A 
> 
> 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 
> 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: 
> 
> 856AA88A 
> 
> 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 
> 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: 
> 
> 856AA88A 
> 
> 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 
> 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: 
> 
> 856AA88A 
> 
> 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 
> 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: 
> 
> 856AA88A 
> 
> 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 
> 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: 
> 
> 856AA88A 
> 
> 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 
> 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: 
> 
> 856AA88A 
> 
> 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 
> 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: 
> 
> 856AA88A 
> 
> 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 
> 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: 
> 
> 856AA88A 
> 
> 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 
> 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: 
> 
> 856AA88A 
> 
> 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 
> 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: 
> 
> 856AA88A 
> 
> 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 
> 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: 
> 
> 856AA88A 
> 
> 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 
> 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: 
> 
> 856AA88A 
> 
> 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 
> 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: 
> 
> 856AA88A 
> 
> 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 
> 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: 
> 
> 856AA88A 
> 
> 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 
> 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: 
> 
> 856AA88A 
> 
> 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 
> 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: 
> 
> 856AA88A 
> 
> 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 
> 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: 
> 
> 856AA88A 
> 
> 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 
> 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: 
> 
> 856AA88A 
> 
> 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 
> 
> 
> 
> =================================
> Kevin W. Gagel
> Network Administrator
> Information Technology Services
> (250) 562-2131 local 5448
> My Blog:
> http://mail.cnc.bc.ca/blogs/gagel
> My File share:
> http://mail.cnc.bc.ca/users/gagel
> 
> -------------------------------------------------------------------
> The College of New Caledonia, Visit us at http://www.cnc.bc.ca
> Virus scanning is done on all incoming and outgoing email.
> Anti-spam information for CNC can be found at http://gateway.cnc.bc.ca
> -------------------------------------------------------------------

Mime
View raw message