spamassassin-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mathias Homann <ad...@eregion.de>
Subject Re: how to keep updated against german spam?
Date Tue, 10 Jun 2008 20:37:43 GMT
Am Dienstag, 10. Juni 2008 schrieb Michael Monnerie:
> On Dienstag, 10. Juni 2008 peter pilsl wrote:
> > I run spamassassin 3.2.3 and every few weeks a new wave of german
> > SPAM hits our servers that are not detected by spamassassin...
> >
> > Is there a webpage where I can get new rules? or any channel I
> > can subscribe for sa-update?
> >
> > I also have a question about sa-update and new channels? If I add
> > a new channel that provides new rulesets, do I have to add this
> > new rules to my local.cf or are they used automatically as if
> > they were sa-rules themselfes?
>
> I am the maintainer of the GERMAN ruleset. You can download it in
> various ways. From the comment within that ruleset:
>
> # License: Artistic - see http://www.rulesemporium.com/license.txt
> # Maintainer: Michael Monnerie (sare-german@zmi.at) from
> it-management.at # How to get it:
> # SpamAssassin Channel: 70_zmi_german.cf.zmi.sa-update.dostech.net
> # Also via RDJ (RulesDuJour) as: ZMI_GERMAN
> # RDJ is available at
> http://www.exit0.us/index.php?pagename=RulesDuJour # Home:
> http://sa.zmi.at/rulesets/70_zmi_german.cf
> # HOWTO contribute:
> # - write and --lint your own rules
> # - be sure it hits more than just one spam
> # - try to write rules similar to how we write them recently (see
> the #   latest body rulesets (the last ones!) to get an example) #
> - be sure it actually *is* spam, not just a newsletter from a
> company #   who bought your e-mail address from another company
> (they often don't know...) # - send your rules to the maintainer
> (see above) together with the licence #   (which MUST be "Artistic"
> for me to include it, or you grant me rights #    to redistribute
> it under the "Artistic" licence)
>
> mfg zmi

from sa-update -D:

[12517] dbg: http: GET request, 
http://daryl.dostech.ca/sa-update/zmi/70_zmi_german.cf/200806051042.tar.gz.asc
[12517] dbg: sha1: verification wanted: 
91eaa15f9a096c202a18b9f5f858fc25058643aa
[12517] dbg: sha1: verification result: 
91eaa15f9a096c202a18b9f5f858fc25058643aa
[12517] dbg: channel: populating temp content file
[12517] dbg: gpg: populating temp signature file
[12517] dbg: gpg: calling gpg
[12517] dbg: gpg: gpg: Signature made Do 05 Jun 2008 10:50:57 CEST 
using DSA key ID 856AA88A
[12517] dbg: gpg: [GNUPG:] ERRSIG 3C5C05EB856AA88A 17 2 00 1212655857 
9
[12517] dbg: gpg: [GNUPG:] NO_PUBKEY 3C5C05EB856AA88A
[12517] dbg: gpg: gpg: Can't check signature: public key not found
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



-- 
gpg key fingerprint: 5F64 4C92 9B77 DE37 D184  C5F9 B013 44E7 27BD 
763C

Mime
View raw message