update does not work correctly?

2009-10-23 Thread klopp76
Hi,

 

I use Spamassassin 3.2.5 with CentOS

On October 20 I startet an update with this commands:

sa-update --channel updates.spamassassin.org

 

When I start now the update, the date of the folder and file in
/var/lib/spamassassin/3.002005 does not change. It is still the October 20

 

Did anyone an idea why the date does not change?

 

Thanks

 

 



Re: update does not work correctly?

2009-10-23 Thread McDonald, Dan
On Fri, 2009-10-23 at 13:02 +0200, klop...@gmx.de wrote:
 Hi,
 
  
 
 I use Spamassassin 3.2.5 with CentOS
 
 On October 20 I startet an update with this commands:
 
 sa-update --channel updates.spamassassin.org
 
  
 
 When I start now the update, the date of the folder and file
 in /var/lib/spamassassin/3.002005 does not change. It is still the
 October 20
 
  
 
 Did anyone an idea why the date does not change?

There hasn't been an update.

Look at the first line
of /var/lib/spamassassin/3.002005/updates_spamassassin_org.cf, and you
will see the current version:
# UPDATE version 795855

Then check DNS to see if a newer version has been published:
$ dig 5.2.3.updates.spamassassin.org txt
...
;; ANSWER SECTION:
5.2.3.updates.spamassassin.org. 3600 IN TXT 795855

Same version.  No change.  Updates.spamassassin.org isn't updated very
often, not since July.  

-- 
Daniel J McDonald, CCIE # 2495, CISSP # 78281, CNX
www.austinenergy.com


signature.asc
Description: This is a digitally signed message part


Re: update does not work correctly?

2009-10-23 Thread Matt Kettler
klop...@gmx.de wrote:

 Hi,

  

 I use Spamassassin 3.2.5 with CentOS

 On October 20 I startet an update with this commands:

 sa-update --channel updates.spamassassin.org

  

 When I start now the update, the date of the folder and file in
 /var/lib/spamassassin/3.002005 does not change. It is still the
 October 20

  

 Did anyone an idea why the date does not change?

Updates are published as needed, which at times means there may be
updates every day, and other times it may be a several months between
releases.

In general spam signatures are fairly broad and generic, and need to be
updated *MUCH* less often than virus signatures. Virus signatures target
a single virus at a time, thus need updating for every new variant,
hence the very frequent releases. SA rules target a generic trait of a
message, and only need updating when there is radical change in the spam
stream.

Looking at the SVN tags, the last update to rules for the 3.2 branch was
pushed back on July 20th.