Summary: | mail-filter/spamassassin: sa-update doesn't work anymore since upgrading to app-crypt/gnupg-2.0.9 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | valli <gentoo> |
Component: | New packages | Assignee: | Gentoo Perl team <perl> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | CC: | dilfridge, graham, ooblick |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
valli
2008-04-18 09:38:42 UTC
A workaround is to add the '--nogpg' option to the sa-update command line. There's an entry on the spamassassin wiki about this: http://wiki.apache.org/spamassassin/SaUpdateKeyNotCrossCertified Follow the instructions there to import the new GPG key: wget http://spamassassin.apache.org/updates/GPG.KEY sa-update --import GPG.KEY sa-update should now work. Just as additional comment, this seems to be fixed upstream as of spamassassin svn rev. 610699, but not in any release yet. See https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5775 This is fixed in spamassassin 3.2.5. From the spamassassin 3.2.5 announcement: ... - bug 5775: newer gpg versions require keys to be cross-certified (backsig). Did a cross-verify on our sa-update public key and re-exported. If you are already seeing "GPG validation failed" errors from sa-update, see http://wiki.apache.org/spamassassin/SaUpdateKeyNotCrossCertified .) ... (http://svn.apache.org/repos/asf/spamassassin/branches/3.2/build/announcements/3.2.5.txt) Marked as duplicate of bug #228557 *** This bug has been marked as a duplicate of bug 228557 *** |