updates being published

[Justin Mason <jm...@jmason.org>]

Using SVN trunk, this now works:

  sudo sa-update && sudo /etc/init.d/spamassassin reload


note that you need to import the GPG key:

    wget http://spamassassin.apache.org/updates/GPG.KEY
    gpg --import GPG.KEY


The updates are being distributed via Coral (http://coralcdn.org/) to save
load.  They are generated nightly based on "rules/active.list", which is
generated based on freqs from the previous day's mass-checks, and sandbox
rules will be published via updates if they pass the publishing criteria
-- all as per recent discussions on this list. 

So if you've got good, fresh rules, it might be worth throwing them
into a sandbox now, and see if they get published ;)

--j.

Re: updates being published

[Henry Stern <he...@stern.ca>]

There's a problem with the updates_spamassassin_org.cf file.  It contains:

include updates_spamassassin_org/MIRRORED.BY
include updates_spamassassin_org/languages
include updates_spamassassin_org/triplets.txt
include updates_spamassassin_org/user_prefs.template

The first file does not exist.  The middle two files being included
causes about 50k "cannot parse" messages to appear in the syslog.  The
third should probably not be included as it is a template.

Cheers,
Henry

Justin Mason wrote:
> Using SVN trunk, this now works:
>
>   sudo sa-update && sudo /etc/init.d/spamassassin reload
>
>
> note that you need to import the GPG key:
>
>     wget http://spamassassin.apache.org/updates/GPG.KEY
>     gpg --import GPG.KEY
>
>
> The updates are being distributed via Coral (http://coralcdn.org/) to save
> load.  They are generated nightly based on "rules/active.list", which is
> generated based on freqs from the previous day's mass-checks, and sandbox
> rules will be published via updates if they pass the publishing criteria
> -- all as per recent discussions on this list.
>
> So if you've got good, fresh rules, it might be worth throwing them
> into a sandbox now, and see if they get published ;)
>
> --j.
>

Re: updates being published

[Theo Van Dinter <fe...@apache.org>]

On Sat, Jan 14, 2006 at 01:13:08PM -0500, Warren Togami wrote:
> Cool.  Is it in the plans for sa-update to be usable with the 3.1.1 
> release too?

I sadly haven't been too involved in getting sa-update actually going,
but at the moment it looks like it's just 3.2.  There were a lot of
sa-update patches in 3.2, and that's the only update out there currently.

BTW: for Justin/etc, it looks like the update that's out there is
specifically for 3.2.0 only, ie, it's not *.2.3.updates.spamassassin.org,
which would let it be used for all 3.2 releases.

-- 
Randomly Generated Tagline:
"Open Source UNIX is shaped by people who use it.  Microsoft shapes NT
 to respond to competitive threats."         - Nicholas Petreley

Re: updates being published

[Warren Togami <wt...@redhat.com>]

Justin Mason wrote:
> Using SVN trunk, this now works:
> 
>   sudo sa-update && sudo /etc/init.d/spamassassin reload
> 

Cool.  Is it in the plans for sa-update to be usable with the 3.1.1 
release too?

Warren Togami
wtogami@redhat.com