Matt Kettler wrote:
Sn!per wrote:
Quoting Matt Kettler <[EMAIL PROTECTED]>:
ie: the two most recent for the 3.2 branch are:
# sa-update_3.2_20080114123639/
# sa-update_3.2_20080114144817/
Which were both made on January 14th, 2008. I suspect the rest is a
timestamp, but I'm not entirely sure. If it is, the two were pushed
a little over 2 hours apart.
The 3.3 branch has had more recent updates, but at present that's
still a development branch, so the devs are more free to push rules
to it that are somewhat experimental.
I have this in my cron to update the rules:
00 * * * * /usr/bin/sa-update --gpgkey 6C6191E3 --channel
sought.rules.yerp.org --gpgkey
D1C035168C1EBC08464946DA258CDB3ABDE9DC10 --channel
saupdates.openprotect.com --channel updates.spamassassin.org
--allowplugins
But since early Feb, I didn't see any update taking place. I have
these in /usr/share/spamassassin:
Well, as I said above no updates have been published since Jan 14th.
So I would not expect any.
but Justin rules were updated in the meantime.
However, sa-update's don't go in /usr/share/spamassassin. You'll
*NEVER* see updates if you keep looking there. Feb 7th should be the
date of your install.
Updates go into /var/lib/spamassassin/<version
number>/updates_spamassassin_org/
or
/var/db/spamassassin/... if using FreeBSD ports
/var/spamassassin/... if using pkgsrc (NetBSD, ... )
If you look there, there should be files that are newer than
/usr/share/spamassassin, but you'll only have found an update once
since install. You won't find any again until a dev chooses to push
rules to 3.2 That could be tomorrow, it could be a year from now.
Don't expect daily updates. SpamAssassin is not an anti-virus product.
We don't need new rules for each and every spam message, we only need
them when there's a very significant mutation.
