Re: SA-Update not updating DB

[@lbutlr]

On 17 Nov 2017, at 05:32, David Jones  wrote:
> If I don't hear any objections or negative feedback in the next 36 hours, I 
> will enable DNS updates tomorrow so sa-update will start automatically 
> updating rulesets on Sunday morning.



Excellent!



-- 
Apple broke AppleScripting signatures in Mail.app, so no random signatures.

Re: SA-Update not updating DB

[Dave Wreski]

On 11/17/2017 11:39 AM, Jari Fredriksson wrote:




David Jones  kirjoitti 16.11.2017 kello 15.22:

REV=1815298
wget http://sa-update.ena.com/${REV}.tar.gz
wget http://sa-update.ena.com/${REV}.tar.gz.sha1
wget http://sa-update.ena.com/${REV}.tar.gz.asc
sa-update -v --install ${REV}.tar.gz


+1 for sunday. I installed this now to my farm and will keep and eye on it thru 
weekend.


+1 for Sunday here too. We've installed it all around and doing great so 
far. Thanks everyone for the amazing work.


Thanks,
Dave

Re: SA-Update not updating DB

[Jari Fredriksson]

> David Jones  kirjoitti 16.11.2017 kello 15.22:
> 
> REV=1815298
> wget http://sa-update.ena.com/${REV}.tar.gz
> wget http://sa-update.ena.com/${REV}.tar.gz.sha1
> wget http://sa-update.ena.com/${REV}.tar.gz.asc
> sa-update -v --install ${REV}.tar.gz

+1 for sunday. I installed this now to my farm and will keep and eye on it thru 
weekend.

br. jarif


signature.asc
Description: Message signed with OpenPGP

Re: SA-Update not updating DB

[Matthew Broadhead]

sorry +1 one for sunday

On 17/11/2017 15:14, David Jones wrote:

Is that +1 for Sunday start or Monday start?

Dave

On 11/17/2017 07:47 AM, Matthew Broadhead wrote:

+1 (non binding) sounds good to me

On 17/11/2017 14:45, David Jones wrote:

On 11/17/2017 06:32 AM, David Jones wrote:

On 11/16/2017 05:09 PM, Richard Doyle wrote:

Update applied, no issues.



I saw 18 testers in my web logs for yesterday's $REV. Thanks to 
everyone that are helping by testing.



On 11/16/2017 05:22 AM, David Jones wrote:
Great news!  Last night's run finally produced a full 
72_scores.cf. Big

thanks to Merijn van den Kroonenberg for helping track down the
remaining issues!  There were about 3 rules difference which 
could be

expected with 8 months difference.

# cat disappeared_rules.txt
ADVANCE_FEE_4_NEW
CN_B2B_SPAMMER
URI_GOOGLE_PROXY

# wc -l 72_scores.cf
149 72_scores.cf

Now 149 lines and we were stuck at around 100 before.

https://svn.apache.org/viewvc/spamassassin/trunk/rulesrc/scores/

WE REALLY NEED TESTERS NOW TO APPLY THIS UPDATE AND PROVIDE 
FEEDBACK.  I
would like to enable DNS updates again for sa-update on Sunday or 
Monday

depending on the feedback.

REV=1815298
wget http://sa-update.ena.com/${REV}.tar.gz
wget http://sa-update.ena.com/${REV}.tar.gz.sha1
wget http://sa-update.ena.com/${REV}.tar.gz.asc
sa-update -v --install ${REV}.tar.gz

(reload/restart whatever is calling SA -- spamd, amavis-new, 
mimedefang,

MailScanner, etc.)

I have applied this ruleset to my platforms and will monitor
scoring/blocking over the next couple of days.


On Tue, Nov 14, 2017 at 2:36 PM, John Hardin mailto:jhar...@impsec.org>> wrote:

 On Tue, 14 Nov 2017, Rafael Leiva-Ochoa wrote:

   I am running SpamAssassin 3.4.1, and I have been 
trying to

 update the DB
 located on /var/lib/spamassassin/3.004001/ using 
SA-UPDATE. But,

 it has not
 gotten an update in almost 2 weeks.


 The rules update service has been down due to infrastructure
 problems for a few months now. It is very close (like, 
this week) to

 being fixed.










New version today looks good.  Keep testing and checking your 
scores to make sure they look normal.  Back in June when we tried 
going live with sa-update, the scores were obviously low allowing 
spam through.  This time things look much better and very 
different.  The new 72_scores.cf is complete in size and number of 
lines (151).


cd /tmp
REV=1815423
wget http://sa-update.ena.com/${REV}.tar.gz
wget http://sa-update.ena.com/${REV}.tar.gz.sha1
wget http://sa-update.ena.com/${REV}.tar.gz.asc
sa-update -v --install ${REV}.tar.gz

(reload/restart whatever is calling SA -- spamd, amavis-new, 
mimedefang, MailScanner, etc.)



If I don't hear any objections or negative feedback in the next 36 
hours, I will enable DNS updates tomorrow so sa-update will start 
automatically updating rulesets on Sunday morning.




My thoughts on starting Sunday morning are based on this:
- sa-update won't update for most instances until later on Sunday
- no one would be able to tell of any problems until 24 or 48 hours 
later anyway

- very low risk of problems after testing

I can wait until Monday morning if anyone else thinks we should wait 
one more day.  It's been broken for 8 months so what's one more 
day?  :)

Re: SA-Update not updating DB

[Matthew Broadhead]

+1 (non binding) sounds good to me

On 17/11/2017 14:45, David Jones wrote:

On 11/17/2017 06:32 AM, David Jones wrote:

On 11/16/2017 05:09 PM, Richard Doyle wrote:

Update applied, no issues.



I saw 18 testers in my web logs for yesterday's $REV.  Thanks to 
everyone that are helping by testing.



On 11/16/2017 05:22 AM, David Jones wrote:
Great news!  Last night's run finally produced a full 72_scores.cf. 
Big

thanks to Merijn van den Kroonenberg for helping track down the
remaining issues!  There were about 3 rules difference which could be
expected with 8 months difference.

# cat disappeared_rules.txt
ADVANCE_FEE_4_NEW
CN_B2B_SPAMMER
URI_GOOGLE_PROXY

# wc -l 72_scores.cf
149 72_scores.cf

Now 149 lines and we were stuck at around 100 before.

https://svn.apache.org/viewvc/spamassassin/trunk/rulesrc/scores/

WE REALLY NEED TESTERS NOW TO APPLY THIS UPDATE AND PROVIDE 
FEEDBACK.  I
would like to enable DNS updates again for sa-update on Sunday or 
Monday

depending on the feedback.

REV=1815298
wget http://sa-update.ena.com/${REV}.tar.gz
wget http://sa-update.ena.com/${REV}.tar.gz.sha1
wget http://sa-update.ena.com/${REV}.tar.gz.asc
sa-update -v --install ${REV}.tar.gz

(reload/restart whatever is calling SA -- spamd, amavis-new, 
mimedefang,

MailScanner, etc.)

I have applied this ruleset to my platforms and will monitor
scoring/blocking over the next couple of days.


On Tue, Nov 14, 2017 at 2:36 PM, John Hardin mailto:jhar...@impsec.org>> wrote:

 On Tue, 14 Nov 2017, Rafael Leiva-Ochoa wrote:

   I am running SpamAssassin 3.4.1, and I have been 
trying to

 update the DB
 located on /var/lib/spamassassin/3.004001/ using 
SA-UPDATE. But,

 it has not
 gotten an update in almost 2 weeks.


 The rules update service has been down due to infrastructure
 problems for a few months now. It is very close (like, this 
week) to

 being fixed.










New version today looks good.  Keep testing and checking your scores 
to make sure they look normal.  Back in June when we tried going live 
with sa-update, the scores were obviously low allowing spam through.  
This time things look much better and very different.  The new 
72_scores.cf is complete in size and number of lines (151).


cd /tmp
REV=1815423
wget http://sa-update.ena.com/${REV}.tar.gz
wget http://sa-update.ena.com/${REV}.tar.gz.sha1
wget http://sa-update.ena.com/${REV}.tar.gz.asc
sa-update -v --install ${REV}.tar.gz

(reload/restart whatever is calling SA -- spamd, amavis-new, 
mimedefang, MailScanner, etc.)



If I don't hear any objections or negative feedback in the next 36 
hours, I will enable DNS updates tomorrow so sa-update will start 
automatically updating rulesets on Sunday morning.




My thoughts on starting Sunday morning are based on this:
- sa-update won't update for most instances until later on Sunday
- no one would be able to tell of any problems until 24 or 48 hours 
later anyway

- very low risk of problems after testing

I can wait until Monday morning if anyone else thinks we should wait 
one more day.  It's been broken for 8 months so what's one more day?  :)

Re: SA-Update not updating DB

[David Jones]

On 11/17/2017 06:32 AM, David Jones wrote:

On 11/16/2017 05:09 PM, Richard Doyle wrote:

Update applied, no issues.



I saw 18 testers in my web logs for yesterday's $REV.  Thanks to 
everyone that are helping by testing.



On 11/16/2017 05:22 AM, David Jones wrote:

Great news!  Last night's run finally produced a full 72_scores.cf. Big
thanks to Merijn van den Kroonenberg for helping track down the
remaining issues!  There were about 3 rules difference which could be
expected with 8 months difference.

# cat disappeared_rules.txt
ADVANCE_FEE_4_NEW
CN_B2B_SPAMMER
URI_GOOGLE_PROXY

# wc -l 72_scores.cf
149 72_scores.cf

Now 149 lines and we were stuck at around 100 before.

https://svn.apache.org/viewvc/spamassassin/trunk/rulesrc/scores/

WE REALLY NEED TESTERS NOW TO APPLY THIS UPDATE AND PROVIDE FEEDBACK.  I
would like to enable DNS updates again for sa-update on Sunday or Monday
depending on the feedback.

REV=1815298
wget http://sa-update.ena.com/${REV}.tar.gz
wget http://sa-update.ena.com/${REV}.tar.gz.sha1
wget http://sa-update.ena.com/${REV}.tar.gz.asc
sa-update -v --install ${REV}.tar.gz

(reload/restart whatever is calling SA -- spamd, amavis-new, mimedefang,
MailScanner, etc.)

I have applied this ruleset to my platforms and will monitor
scoring/blocking over the next couple of days.


On Tue, Nov 14, 2017 at 2:36 PM, John Hardin mailto:jhar...@impsec.org>> wrote:

 On Tue, 14 Nov 2017, Rafael Leiva-Ochoa wrote:

   I am running SpamAssassin 3.4.1, and I have been trying to
 update the DB
 located on /var/lib/spamassassin/3.004001/ using 
SA-UPDATE. But,

 it has not
 gotten an update in almost 2 weeks.


 The rules update service has been down due to infrastructure
 problems for a few months now. It is very close (like, this 
week) to

 being fixed.










New version today looks good.  Keep testing and checking your scores to 
make sure they look normal.  Back in June when we tried going live with 
sa-update, the scores were obviously low allowing spam through.  This 
time things look much better and very different.  The new 72_scores.cf 
is complete in size and number of lines (151).


cd /tmp
REV=1815423
wget http://sa-update.ena.com/${REV}.tar.gz
wget http://sa-update.ena.com/${REV}.tar.gz.sha1
wget http://sa-update.ena.com/${REV}.tar.gz.asc
sa-update -v --install ${REV}.tar.gz

(reload/restart whatever is calling SA -- spamd, amavis-new, mimedefang, 
MailScanner, etc.)



If I don't hear any objections or negative feedback in the next 36 
hours, I will enable DNS updates tomorrow so sa-update will start 
automatically updating rulesets on Sunday morning.




My thoughts on starting Sunday morning are based on this:
- sa-update won't update for most instances until later on Sunday
- no one would be able to tell of any problems until 24 or 48 hours 
later anyway

- very low risk of problems after testing

I can wait until Monday morning if anyone else thinks we should wait one 
more day.  It's been broken for 8 months so what's one more day?  :)


--
David Jones

Re: SA-Update not updating DB

[Kevin A. McGrail]

On 11/17/2017 7:32 AM, David Jones wrote:
I saw 18 testers in my web logs for yesterday's $REV.  Thanks to 
everyone that are helping by testing.
NOTE: I got many many more.  I had them update from normal sa-update 
though or mailed the tar files.
New version today looks good.  Keep testing and checking your scores 
to make sure they look normal.  Back in June when we tried going live 
with sa-update, the scores were obviously low allowing spam through.  
This time things look much better and very different. The new 
72_scores.cf is complete in size and number of lines (151).

In production for me after a spot check!
If I don't hear any objections or negative feedback in the next 36 
hours, I will enable DNS updates tomorrow so sa-update will start 
automatically updating rulesets on Sunday morning.


+1


Regards,

KAM

Re: SA-Update not updating DB

[David Jones]

On 11/16/2017 05:09 PM, Richard Doyle wrote:

Update applied, no issues.



I saw 18 testers in my web logs for yesterday's $REV.  Thanks to 
everyone that are helping by testing.



On 11/16/2017 05:22 AM, David Jones wrote:

Great news!  Last night's run finally produced a full 72_scores.cf. Big
thanks to Merijn van den Kroonenberg for helping track down the
remaining issues!  There were about 3 rules difference which could be
expected with 8 months difference.

# cat disappeared_rules.txt
ADVANCE_FEE_4_NEW
CN_B2B_SPAMMER
URI_GOOGLE_PROXY

# wc -l 72_scores.cf
149 72_scores.cf

Now 149 lines and we were stuck at around 100 before.

https://svn.apache.org/viewvc/spamassassin/trunk/rulesrc/scores/

WE REALLY NEED TESTERS NOW TO APPLY THIS UPDATE AND PROVIDE FEEDBACK.  I
would like to enable DNS updates again for sa-update on Sunday or Monday
depending on the feedback.

REV=1815298
wget http://sa-update.ena.com/${REV}.tar.gz
wget http://sa-update.ena.com/${REV}.tar.gz.sha1
wget http://sa-update.ena.com/${REV}.tar.gz.asc
sa-update -v --install ${REV}.tar.gz

(reload/restart whatever is calling SA -- spamd, amavis-new, mimedefang,
MailScanner, etc.)

I have applied this ruleset to my platforms and will monitor
scoring/blocking over the next couple of days.


On Tue, Nov 14, 2017 at 2:36 PM, John Hardin mailto:jhar...@impsec.org>> wrote:

 On Tue, 14 Nov 2017, Rafael Leiva-Ochoa wrote:

   I am running SpamAssassin 3.4.1, and I have been trying to
 update the DB
 located on /var/lib/spamassassin/3.004001/ using SA-UPDATE. But,
 it has not
 gotten an update in almost 2 weeks.


 The rules update service has been down due to infrastructure
 problems for a few months now. It is very close (like, this week) to
 being fixed.










New version today looks good.  Keep testing and checking your scores to 
make sure they look normal.  Back in June when we tried going live with 
sa-update, the scores were obviously low allowing spam through.  This 
time things look much better and very different.  The new 72_scores.cf 
is complete in size and number of lines (151).


cd /tmp
REV=1815423
wget http://sa-update.ena.com/${REV}.tar.gz
wget http://sa-update.ena.com/${REV}.tar.gz.sha1
wget http://sa-update.ena.com/${REV}.tar.gz.asc
sa-update -v --install ${REV}.tar.gz

(reload/restart whatever is calling SA -- spamd, amavis-new, mimedefang, 
MailScanner, etc.)



If I don't hear any objections or negative feedback in the next 36 
hours, I will enable DNS updates tomorrow so sa-update will start 
automatically updating rulesets on Sunday morning.


--
David Jones

Re: SA-Update not updating DB

[Rafael Leiva-Ochoa]

Updated mine, it seems to be working so far.

On Wed, Nov 15, 2017 at 5:39 AM, Kevin A. McGrail  wrote:

> On 11/15/2017 8:27 AM, David Jones wrote:
>
>>
>> We are getting closer to having complete rulesets working again.
>>
>> NOTE: The latest ruleset generated hours ago is still not quite complete
>> but I think it's safe for testing.  I have applied this ruleset to my
>> platforms.
>>
>> REV=1815188
>> wget http://sa-update.ena.com/${REV}.tar.gz
>> wget http://sa-update.ena.com/${REV}.tar.gz.sha1
>> wget http://sa-update.ena.com/${REV}.tar.gz.asc
>> sa-update -v --install ${REV}.tar.gz
>>
> FYI to others, I am testing in production and even the not quite perfect
> ones haven't had a large impact on production.
>
> Best,
> KAM
>

Re: SA-Update not updating DB

[Chris]

On Thu, 2017-11-16 at 09:06 -0600, David Jones wrote:
> On 11/16/2017 08:57 AM, Chris wrote:
> > 
> > On Thu, 2017-11-16 at 07:22 -0600, David Jones wrote:
> > > 
> > > Great news!  Last night's run finally produced a full
> > > 72_scores.cf.
> > > Big
> > > thanks to Merijn van den Kroonenberg for helping track down the
> > > remaining issues!  There were about 3 rules difference which
> > > could
> > > be
> > > expected with 8 months difference.
> > > 
> > > # cat disappeared_rules.txt
> > > ADVANCE_FEE_4_NEW
> > > CN_B2B_SPAMMER
> > > URI_GOOGLE_PROXY
> > > 
> > > # wc -l 72_scores.cf
> > > 149 72_scores.cf
> > > 
> > > Now 149 lines and we were stuck at around 100 before.
> > > 
> > > https://svn.apache.org/viewvc/spamassassin/trunk/rulesrc/scores/
> > > 
> > > WE REALLY NEED TESTERS NOW TO APPLY THIS UPDATE AND PROVIDE
> > > FEEDBACK.  I
> > > would like to enable DNS updates again for sa-update on Sunday or
> > > Monday
> > > depending on the feedback.
> > > 
> > > REV=1815298
> > > wget http://sa-update.ena.com/${REV}.tar.gz
> > > wget http://sa-update.ena.com/${REV}.tar.gz.sha1
> > > wget http://sa-update.ena.com/${REV}.tar.gz.asc
> > > sa-update -v --install ${REV}.tar.gz
> > > 
> > > (reload/restart whatever is calling SA -- spamd, amavis-new,
> > > mimedefang,
> > > MailScanner, etc.)
> > > 
> > > I have applied this ruleset to my platforms and will monitor
> > > scoring/blocking over the next couple of days.
> > > 
> > Hmm, the file doesn't seem to be able to be found unless of course
> > I
> > did something incorrectly:
> > 
> > chris@localhost:~/Downloads$ wget http://sa-update.ena.com/${REV}.t
> > ar.g
> > z
> > --2017-11-16 08:51:50--  http://sa-update.ena.com/.tar.gz
> > Resolving sa-update.ena.com (sa-update.ena.com)... 96.4.1.5,
> > 96.5.1.5
> > Connecting to sa-update.ena.com (sa-update.ena.com)|96.4.1.5|:80...
> > connected.
> > HTTP request sent, awaiting response... 404 Not Found
> > 2017-11-16 08:51:50 ERROR 404: Not Found.
> > 
> Make sure you ran the "REV=1815298" line first to set the variable
> that 
> the next 4 lines use with "${REV}".
> 
I got it David and Dave. Thanks for straightening me out.
-- 
Chris
KeyID 0xE372A7DA98E6705C
31.11972; -97.90167 (Elev. 1092 ft)
16:20:55 up 9 days, 7:52, 1 user, load average: 1.10, 0.72, 0.74
Description:Ubuntu 16.04.3 LTS, kernel 4.10.0-38-generic


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

Re: SA-Update not updating DB

[Matthew Broadhead]

Hi,
I downloaded and applied the update on CentOS 7 
3.10.0-693.2.2.el7.x86_64.  spamassassin-3.4.0-2.el7.x86_64. everything 
seems to be working fine so far.  I will let you know if there are any 
issues

Thanks for all the work on the update,
Matthew

On 16/11/2017 14:22, David Jones wrote:
Great news!  Last night's run finally produced a full 72_scores.cf. 
Big thanks to Merijn van den Kroonenberg for helping track down the 
remaining issues!  There were about 3 rules difference which could be 
expected with 8 months difference.


# cat disappeared_rules.txt
ADVANCE_FEE_4_NEW
CN_B2B_SPAMMER
URI_GOOGLE_PROXY

# wc -l 72_scores.cf
149 72_scores.cf

Now 149 lines and we were stuck at around 100 before.

https://svn.apache.org/viewvc/spamassassin/trunk/rulesrc/scores/

WE REALLY NEED TESTERS NOW TO APPLY THIS UPDATE AND PROVIDE FEEDBACK.  
I would like to enable DNS updates again for sa-update on Sunday or 
Monday depending on the feedback.


REV=1815298
wget http://sa-update.ena.com/${REV}.tar.gz
wget http://sa-update.ena.com/${REV}.tar.gz.sha1
wget http://sa-update.ena.com/${REV}.tar.gz.asc
sa-update -v --install ${REV}.tar.gz

(reload/restart whatever is calling SA -- spamd, amavis-new, 
mimedefang, MailScanner, etc.)


I have applied this ruleset to my platforms and will monitor 
scoring/blocking over the next couple of days.


On Tue, Nov 14, 2017 at 2:36 PM, John Hardin > wrote:


    On Tue, 14 Nov 2017, Rafael Leiva-Ochoa wrote:

  I am running SpamAssassin 3.4.1, and I have been trying to
    update the DB
    located on /var/lib/spamassassin/3.004001/ using SA-UPDATE. 
But,

    it has not
    gotten an update in almost 2 weeks.


    The rules update service has been down due to infrastructure
    problems for a few months now. It is very close (like, this 
week) to

    being fixed.

    --   John Hardin KA7OHZ http://www.impsec.org/~jhardin/
    
    jhar...@impsec.org  FALaholic #11174 
    pgpk -a jhar...@impsec.org 
  key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 
B873 2E79

---
   We should endeavour to teach our children to be gun-proof
   rather than trying to design our guns to be child-proof
---
  229 days since the first commercial re-flight of an orbital
    booster (SpaceX)

Re: SA-Update not updating DB

[Dave Wreski]

REV=1815298
wget http://sa-update.ena.com/${REV}.tar.gz
wget http://sa-update.ena.com/${REV}.tar.gz.sha1
wget http://sa-update.ena.com/${REV}.tar.gz.asc
sa-update -v --install ${REV}.tar.gz

(reload/restart whatever is calling SA -- spamd, amavis-new,
mimedefang,
MailScanner, etc.)

I have applied this ruleset to my platforms and will monitor
scoring/blocking over the next couple of days.


Hmm, the file doesn't seem to be able to be found unless of course I
did something incorrectly:

chris@localhost:~/Downloads$ wget http://sa-update.ena.com/${REV}.tar.g
z
--2017-11-16 08:51:50--  http://sa-update.ena.com/.tar.gz
Resolving sa-update.ena.com (sa-update.ena.com)... 96.4.1.5, 96.5.1.5
Connecting to sa-update.ena.com (sa-update.ena.com)|96.4.1.5|:80...
connected.
HTTP request sent, awaiting response... 404 Not Found
2017-11-16 08:51:50 ERROR 404: Not Found.


You forgot to set the REV environment variable first. Just copy the text 
including the REV=1815298 and paste on the command-line as root and it 
should work.


Regards,
Dave

Re: SA-Update not updating DB

[David Jones]

On 11/16/2017 08:57 AM, Chris wrote:

On Thu, 2017-11-16 at 07:22 -0600, David Jones wrote:

Great news!  Last night's run finally produced a full 72_scores.cf.
Big
thanks to Merijn van den Kroonenberg for helping track down the
remaining issues!  There were about 3 rules difference which could
be
expected with 8 months difference.

# cat disappeared_rules.txt
ADVANCE_FEE_4_NEW
CN_B2B_SPAMMER
URI_GOOGLE_PROXY

# wc -l 72_scores.cf
149 72_scores.cf

Now 149 lines and we were stuck at around 100 before.

https://svn.apache.org/viewvc/spamassassin/trunk/rulesrc/scores/

WE REALLY NEED TESTERS NOW TO APPLY THIS UPDATE AND PROVIDE
FEEDBACK.  I
would like to enable DNS updates again for sa-update on Sunday or
Monday
depending on the feedback.

REV=1815298
wget http://sa-update.ena.com/${REV}.tar.gz
wget http://sa-update.ena.com/${REV}.tar.gz.sha1
wget http://sa-update.ena.com/${REV}.tar.gz.asc
sa-update -v --install ${REV}.tar.gz

(reload/restart whatever is calling SA -- spamd, amavis-new,
mimedefang,
MailScanner, etc.)

I have applied this ruleset to my platforms and will monitor
scoring/blocking over the next couple of days.


Hmm, the file doesn't seem to be able to be found unless of course I
did something incorrectly:

chris@localhost:~/Downloads$ wget http://sa-update.ena.com/${REV}.tar.g
z
--2017-11-16 08:51:50--  http://sa-update.ena.com/.tar.gz
Resolving sa-update.ena.com (sa-update.ena.com)... 96.4.1.5, 96.5.1.5
Connecting to sa-update.ena.com (sa-update.ena.com)|96.4.1.5|:80...
connected.
HTTP request sent, awaiting response... 404 Not Found
2017-11-16 08:51:50 ERROR 404: Not Found.



Make sure you ran the "REV=1815298" line first to set the variable that 
the next 4 lines use with "${REV}".


--
David Jones

Re: SA-Update not updating DB

[Chris]

On Thu, 2017-11-16 at 07:22 -0600, David Jones wrote:
> Great news!  Last night's run finally produced a full 72_scores.cf.
> Big 
> thanks to Merijn van den Kroonenberg for helping track down the 
> remaining issues!  There were about 3 rules difference which could
> be 
> expected with 8 months difference.
> 
> # cat disappeared_rules.txt
> ADVANCE_FEE_4_NEW
> CN_B2B_SPAMMER
> URI_GOOGLE_PROXY
> 
> # wc -l 72_scores.cf
> 149 72_scores.cf
> 
> Now 149 lines and we were stuck at around 100 before.
> 
> https://svn.apache.org/viewvc/spamassassin/trunk/rulesrc/scores/
> 
> WE REALLY NEED TESTERS NOW TO APPLY THIS UPDATE AND PROVIDE
> FEEDBACK.  I 
> would like to enable DNS updates again for sa-update on Sunday or
> Monday 
> depending on the feedback.
> 
> REV=1815298
> wget http://sa-update.ena.com/${REV}.tar.gz
> wget http://sa-update.ena.com/${REV}.tar.gz.sha1
> wget http://sa-update.ena.com/${REV}.tar.gz.asc
> sa-update -v --install ${REV}.tar.gz
> 
> (reload/restart whatever is calling SA -- spamd, amavis-new,
> mimedefang, 
> MailScanner, etc.)
> 
> I have applied this ruleset to my platforms and will monitor 
> scoring/blocking over the next couple of days.
> 
Hmm, the file doesn't seem to be able to be found unless of course I
did something incorrectly:

chris@localhost:~/Downloads$ wget http://sa-update.ena.com/${REV}.tar.g
z
--2017-11-16 08:51:50--  http://sa-update.ena.com/.tar.gz
Resolving sa-update.ena.com (sa-update.ena.com)... 96.4.1.5, 96.5.1.5
Connecting to sa-update.ena.com (sa-update.ena.com)|96.4.1.5|:80...
connected.
HTTP request sent, awaiting response... 404 Not Found
2017-11-16 08:51:50 ERROR 404: Not Found.

-- 
Chris
KeyID 0xE372A7DA98E6705C
31.11972; -97.90167 (Elev. 1092 ft)
08:55:52 up 9 days, 27 min, 1 user, load average: 7.24, 2.93, 1.31
Description:Ubuntu 16.04.3 LTS, kernel 4.10.0-38-generic


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

Re: SA-Update not updating DB

[David Jones]

Great news!  Last night's run finally produced a full 72_scores.cf. Big 
thanks to Merijn van den Kroonenberg for helping track down the 
remaining issues!  There were about 3 rules difference which could be 
expected with 8 months difference.


# cat disappeared_rules.txt
ADVANCE_FEE_4_NEW
CN_B2B_SPAMMER
URI_GOOGLE_PROXY

# wc -l 72_scores.cf
149 72_scores.cf

Now 149 lines and we were stuck at around 100 before.

https://svn.apache.org/viewvc/spamassassin/trunk/rulesrc/scores/

WE REALLY NEED TESTERS NOW TO APPLY THIS UPDATE AND PROVIDE FEEDBACK.  I 
would like to enable DNS updates again for sa-update on Sunday or Monday 
depending on the feedback.


REV=1815298
wget http://sa-update.ena.com/${REV}.tar.gz
wget http://sa-update.ena.com/${REV}.tar.gz.sha1
wget http://sa-update.ena.com/${REV}.tar.gz.asc
sa-update -v --install ${REV}.tar.gz

(reload/restart whatever is calling SA -- spamd, amavis-new, mimedefang, 
MailScanner, etc.)


I have applied this ruleset to my platforms and will monitor 
scoring/blocking over the next couple of days.


On Tue, Nov 14, 2017 at 2:36 PM, John Hardin > wrote:


    On Tue, 14 Nov 2017, Rafael Leiva-Ochoa wrote:

  I am running SpamAssassin 3.4.1, and I have been trying to
    update the DB
    located on /var/lib/spamassassin/3.004001/ using SA-UPDATE. But,
    it has not
    gotten an update in almost 2 weeks.


    The rules update service has been down due to infrastructure
    problems for a few months now. It is very close (like, this week) to
    being fixed.

    --   John Hardin KA7OHZ http://www.impsec.org/~jhardin/
    
    jhar...@impsec.org  FALaholic #11174 
    pgpk -a jhar...@impsec.org 
  key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 
B873 2E79

---
   We should endeavour to teach our children to be gun-proof
   rather than trying to design our guns to be child-proof
---
  229 days since the first commercial re-flight of an orbital
    booster (SpaceX)







--
David Jones

Re: SA-Update not updating DB

[Kevin A. McGrail]

On 11/15/2017 8:27 AM, David Jones wrote:


We are getting closer to having complete rulesets working again.

NOTE: The latest ruleset generated hours ago is still not quite 
complete but I think it's safe for testing.  I have applied this 
ruleset to my platforms.


REV=1815188
wget http://sa-update.ena.com/${REV}.tar.gz
wget http://sa-update.ena.com/${REV}.tar.gz.sha1
wget http://sa-update.ena.com/${REV}.tar.gz.asc
sa-update -v --install ${REV}.tar.gz
FYI to others, I am testing in production and even the not quite perfect 
ones haven't had a large impact on production.


Best,
KAM

Re: SA-Update not updating DB

[David Jones]

On 11/14/2017 04:37 PM, Rafael Leiva-Ochoa wrote:

If you need testers, please let me know, I can help.



We are getting closer to having complete rulesets working again.

NOTE: The latest ruleset generated hours ago is still not quite complete 
but I think it's safe for testing.  I have applied this ruleset to my 
platforms.


REV=1815188
wget http://sa-update.ena.com/${REV}.tar.gz
wget http://sa-update.ena.com/${REV}.tar.gz.sha1
wget http://sa-update.ena.com/${REV}.tar.gz.asc
sa-update -v --install ${REV}.tar.gz

(reload/restart whatever is calling SA -- spamd, amavis-new, mimedefang, 
MailScanner, etc.)


We are making another update today that should improve tomorrow's 
rulesets.  Still not quite ready to go live with sa-update but we are 
the closest we have been in 8 months thanks to Merijn's help.


On Tue, Nov 14, 2017 at 2:36 PM, John Hardin > wrote:


On Tue, 14 Nov 2017, Rafael Leiva-Ochoa wrote:

  I am running SpamAssassin 3.4.1, and I have been trying to
update the DB
located on /var/lib/spamassassin/3.004001/ using SA-UPDATE. But,
it has not
gotten an update in almost 2 weeks.


The rules update service has been down due to infrastructure
problems for a few months now. It is very close (like, this week) to
being fixed.

-- 
  John Hardin KA7OHZ http://www.impsec.org/~jhardin/


jhar...@impsec.org     FALaholic #11174 
    pgpk -a jhar...@impsec.org 

  key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
---
   We should endeavour to teach our children to be gun-proof
   rather than trying to design our guns to be child-proof
---
  229 days since the first commercial re-flight of an orbital
booster (SpaceX)





--
David Jones

Re: SA-Update not updating DB

[Rafael Leiva-Ochoa]

If you need testers, please let me know, I can help.

On Tue, Nov 14, 2017 at 2:36 PM, John Hardin  wrote:

> On Tue, 14 Nov 2017, Rafael Leiva-Ochoa wrote:
>
>  I am running SpamAssassin 3.4.1, and I have been trying to update the DB
>> located on /var/lib/spamassassin/3.004001/ using SA-UPDATE. But, it has
>> not
>> gotten an update in almost 2 weeks.
>>
>
> The rules update service has been down due to infrastructure problems for
> a few months now. It is very close (like, this week) to being fixed.
>
> --
>  John Hardin KA7OHZhttp://www.impsec.org/~jhardin/
>  jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org
>  key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
> ---
>   We should endeavour to teach our children to be gun-proof
>   rather than trying to design our guns to be child-proof
> ---
>  229 days since the first commercial re-flight of an orbital booster
> (SpaceX)
>

Re: SA-Update not updating DB

[John Hardin]

On Tue, 14 Nov 2017, Rafael Leiva-Ochoa wrote:


 I am running SpamAssassin 3.4.1, and I have been trying to update the DB
located on /var/lib/spamassassin/3.004001/ using SA-UPDATE. But, it has not
gotten an update in almost 2 weeks.


The rules update service has been down due to infrastructure problems for 
a few months now. It is very close (like, this week) to being fixed.


--
 John Hardin KA7OHZhttp://www.impsec.org/~jhardin/
 jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org
 key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
---
  We should endeavour to teach our children to be gun-proof
  rather than trying to design our guns to be child-proof
---
 229 days since the first commercial re-flight of an orbital booster (SpaceX)

Re: sa-update not updating the rules

[Kevin A. McGrail]

On 1/4/2016 10:25 PM, Muthu N.C wrote:
Thank you Kevin and all for the update. We are started receiving spam 
e-mails from "*.eu" domain in more numbers.May be the latest rules 
might catch those.
Knowing very little about your setup, I'd recommend you post the report 
from a spam that got through to users.



Any rough estimation on when would the latest rules be available?
Sorry, I don't.  I haven't had any time to investigate why we are 
starved on the volunteer submissions.


Best,
KAM



Thanks,
Chollamuthu N.

On Tue, Jan 5, 2016 at 3:32 AM, Kevin A. McGrail > wrote:


On 1/4/2016 4:37 PM, Muthu N.C wrote:

It looks there are latest version of rules available greater than
1720996. But I am not getting that rules. I am seeing now lot of
spam emails comes through.

I see on the below link there are latest version of rules exist.


http://ruleqa.spamassassin.org/?longdatelist=1&perpage=99#r20160104_r1722797_n

Do I need to subscribed to any other channels to get the update?

Sorry but the rule sets aren't published to the world if they
don't pass QA.

regards,
KAM










--
*Kevin A. McGrail*
CEO

Peregrine Computer Consultants Corporation
3927 Old Lee Highway, Suite 102-C
Fairfax, VA 22030-2422

http://www.pccc.com/

703-359-9700 x50 / 800-823-8402 (Toll-Free)
703-798-0171 (wireless)
kmcgr...@pccc.com 

Re: sa-update not updating the rules

[Reindl Harald]

Am 05.01.2016 um 09:52 schrieb Benny Pedersen:

blacklist_from *@*.eu
unblacklist_from *@falsepossitivedomain.eu

no need for rule updates


can you just stop such foolish troll posts all the time?
that works on the server for you and your dog but nowhere else


On January 5, 2016 4:39:10 AM "Muthu N.C"  wrote:


Thank you Kevin and all for the update. We are started receiving spam
e-mails from "*.eu" domain in more numbers.May be the latest rules might
catch those. Any rough estimation on when would the latest rules be
available?

On Tue, Jan 5, 2016 at 3:32 AM, Kevin A. McGrail 
wrote:


On 1/4/2016 4:37 PM, Muthu N.C wrote:

It looks there are latest version of rules available greater than
1720996.
But I am not getting that rules. I am seeing now lot of spam emails
comes
through.

I see on the below link there are latest version of rules exist.




http://ruleqa.spamassassin.org/?longdatelist=1&perpage=99#r20160104_r1722797_n


Do I need to subscribed to any other channels to get the update?

Sorry but the rule sets aren't published to the world if they don't pass
QA.




signature.asc
Description: OpenPGP digital signature

Re: sa-update not updating the rules

[Benny Pedersen]

blacklist_from *@*.eu
unblacklist_from *@falsepossitivedomain.eu

no need for rule updates


On January 5, 2016 4:39:10 AM "Muthu N.C"  wrote:


Thank you Kevin and all for the update. We are started receiving spam
e-mails from "*.eu" domain in more numbers.May be the latest rules might
catch those. Any rough estimation on when would the latest rules be
available?

Thanks,
Chollamuthu N.

On Tue, Jan 5, 2016 at 3:32 AM, Kevin A. McGrail  wrote:


On 1/4/2016 4:37 PM, Muthu N.C wrote:

It looks there are latest version of rules available greater than 1720996.
But I am not getting that rules. I am seeing now lot of spam emails comes
through.

I see on the below link there are latest version of rules exist.



http://ruleqa.spamassassin.org/?longdatelist=1&perpage=99#r20160104_r1722797_n

Do I need to subscribed to any other channels to get the update?

Sorry but the rule sets aren't published to the world if they don't pass
QA.

regards,
KAM

Re: sa-update not updating the rules

[Muthu N.C]

Thank you Kevin and all for the update. We are started receiving spam
e-mails from "*.eu" domain in more numbers.May be the latest rules might
catch those. Any rough estimation on when would the latest rules be
available?

Thanks,
Chollamuthu N.

On Tue, Jan 5, 2016 at 3:32 AM, Kevin A. McGrail  wrote:

> On 1/4/2016 4:37 PM, Muthu N.C wrote:
>
> It looks there are latest version of rules available greater than 1720996.
> But I am not getting that rules. I am seeing now lot of spam emails comes
> through.
>
> I see on the below link there are latest version of rules exist.
>
>
> 
> http://ruleqa.spamassassin.org/?longdatelist=1&perpage=99#r20160104_r1722797_n
>
> Do I need to subscribed to any other channels to get the update?
>
> Sorry but the rule sets aren't published to the world if they don't pass
> QA.
>
> regards,
> KAM
>
>
>
>
>
>
>

Re: sa-update not updating the rules

[Kevin A. McGrail]

On 1/4/2016 4:37 PM, Muthu N.C wrote:
It looks there are latest version of rules available greater than 
1720996. But I am not getting that rules. I am seeing now lot of spam 
emails comes through.


I see on the below link there are latest version of rules exist.

http://ruleqa.spamassassin.org/?longdatelist=1&perpage=99#r20160104_r1722797_n

Do I need to subscribed to any other channels to get the update?
Sorry but the rule sets aren't published to the world if they don't pass 
QA.


regards,
KAM

Re: sa-update not updating the rules

[Reindl Harald]

Am 04.01.2016 um 22:37 schrieb Muthu N.C:

It looks there are latest version of rules available greater than
1720996. But I am not getting that rules. I am seeing now lot of spam
emails comes through.

I see on the below link there are latest version of rules exist.

http://ruleqa.spamassassin.org/?longdatelist=1&perpage=99#r20160104_r1722797_n

Do I need to subscribed to any other channels to get the update?


when one of the core developers tell you there is nothing wrong than 
there is nothing wrong, especially when you see "bb-kmcgrail" in the 
page you linked which is the person you replied to



On Mon, Jan 4, 2016 at 2:24 PM, Kevin A. McGrail mailto:kmcgr...@pccc.com>> wrote:

On 1/4/2016 4:18 PM, Muthu N.C wrote:

I am using the version 3.4.1 spamassassin. I am running sa-update
to update the rules. The rules stopped updating after Dec 21st.
Below is the output when running with debug mode..Any help on
getting the latest update of the rulls will be helpful.

Jan  4 13:55:47.210 [8531] dbg: util: secure_tmpfile created a
temporary file /tmp/.spamassassin85313z6Z0mtmp
Jan  4 13:55:47.210 [8531] dbg: channel: attempting channel
updates.spamassassin.org 
Jan  4 13:55:47.210 [8531] dbg: channel: using existing directory
/var/lib/spamassassin/3.004001/updates_spamassassin_org
Jan  4 13:55:47.210 [8531] dbg: channel: channel cf file
/var/lib/spamassassin/3.004001/updates_spamassassin_org.cf

Jan  4 13:55:47.211 [8531] dbg: channel: channel pre file
/var/lib/spamassassin/3.004001/updates_spamassassin_org.pre
Jan  4 13:55:47.211 [8531] dbg: channel: metadata version =
1720996, from file
/var/lib/spamassassin/3.004001/updates_spamassassin_org.cf

Jan  4 13:55:47.225 [8531] dbg: dns:
1.4.3.updates.spamassassin.org
 => 1720996, parsed as 1720996
Jan  4 13:55:47.226 [8531] dbg: channel: current version is
1720996, new version is 1720996, skipping channel
Jan  4 13:55:47.226 [8531] dbg: diag: updates complete, exiting
with code 1

The system that provides QA for the rules has been starved for
corpora stopping updates from about that time.  There is nothing
wrong with your setup




signature.asc
Description: OpenPGP digital signature

Re: sa-update not updating the rules

[Muthu N.C]

It looks there are latest version of rules available greater than 1720996.
But I am not getting that rules. I am seeing now lot of spam emails comes
through.

I see on the below link there are latest version of rules exist.

http://ruleqa.spamassassin.org/?longdatelist=1&perpage=99#r20160104_r1722797_n

Do I need to subscribed to any other channels to get the update?

Thanks,
Muthu.

On Mon, Jan 4, 2016 at 2:24 PM, Kevin A. McGrail  wrote:

> On 1/4/2016 4:18 PM, Muthu N.C wrote:
>
> I am using the version 3.4.1 spamassassin. I am running sa-update to
> update the rules. The rules stopped updating after Dec 21st. Below is the
> output when running with debug mode..Any help on getting the latest update
> of the rulls will be helpful.
>
> Jan  4 13:55:47.210 [8531] dbg: util: secure_tmpfile created a temporary
> file /tmp/.spamassassin85313z6Z0mtmp
> Jan  4 13:55:47.210 [8531] dbg: channel: attempting channel
> updates.spamassassin.org
> Jan  4 13:55:47.210 [8531] dbg: channel: using existing directory
> /var/lib/spamassassin/3.004001/updates_spamassassin_org
> Jan  4 13:55:47.210 [8531] dbg: channel: channel cf file
> /var/lib/spamassassin/3.004001/updates_spamassassin_org.cf
> Jan  4 13:55:47.211 [8531] dbg: channel: channel pre file
> /var/lib/spamassassin/3.004001/updates_spamassassin_org.pre
> Jan  4 13:55:47.211 [8531] dbg: channel: metadata version = 1720996, from
> file /var/lib/spamassassin/3.004001/updates_spamassassin_org.cf
> Jan  4 13:55:47.225 [8531] dbg: dns: 1.4.3.updates.spamassassin.org =>
> 1720996, parsed as 1720996
> Jan  4 13:55:47.226 [8531] dbg: channel: current version is 1720996, new
> version is 1720996, skipping channel
> Jan  4 13:55:47.226 [8531] dbg: diag: updates complete, exiting with code 1
>
> The system that provides QA for the rules has been starved for corpora
> stopping updates from about that time.  There is nothing wrong with your
> setup.
>
> Regards,
> KAM
>

Re: sa-update not updating the rules

[Kevin A. McGrail]

On 1/4/2016 4:18 PM, Muthu N.C wrote:
I am using the version 3.4.1 spamassassin. I am running sa-update to 
update the rules. The rules stopped updating after Dec 21st. Below is 
the output when running with debug mode..Any help on getting the 
latest update of the rulls will be helpful.


Jan  4 13:55:47.210 [8531] dbg: util: secure_tmpfile created a 
temporary file /tmp/.spamassassin85313z6Z0mtmp
Jan  4 13:55:47.210 [8531] dbg: channel: attempting channel 
updates.spamassassin.org 
Jan  4 13:55:47.210 [8531] dbg: channel: using existing directory 
/var/lib/spamassassin/3.004001/updates_spamassassin_org
Jan  4 13:55:47.210 [8531] dbg: channel: channel cf file 
/var/lib/spamassassin/3.004001/updates_spamassassin_org.cf 

Jan  4 13:55:47.211 [8531] dbg: channel: channel pre file 
/var/lib/spamassassin/3.004001/updates_spamassassin_org.pre
Jan  4 13:55:47.211 [8531] dbg: channel: metadata version = 1720996, 
from file /var/lib/spamassassin/3.004001/updates_spamassassin_org.cf 

Jan  4 13:55:47.225 [8531] dbg: dns: 1.4.3.updates.spamassassin.org 
 => 1720996, parsed as 1720996
Jan  4 13:55:47.226 [8531] dbg: channel: current version is 1720996, 
new version is 1720996, skipping channel
Jan  4 13:55:47.226 [8531] dbg: diag: updates complete, exiting with 
code 1
The system that provides QA for the rules has been starved for corpora 
stopping updates from about that time.  There is nothing wrong with your 
setup.


Regards,
KAM

Re: sa-update not updating the rules

[Jeremy McSpadden]

current version is 1720996
new version is 1720996, skipping channel

1720996 == 1720996

--
Jeremy McSpadden | Flux Labs
Local - 850-250-5590x501 | Mobile - 
850-890-2543
Fax - 850-254-2955 | Toll Free - 
877-699-FLUX
Web - http://www.fluxlabs.net


On Jan 4, 2016, at 3:19 PM, Muthu N.C 
mailto:ncmu...@gmail.com>> wrote:

Jan  4 13:55:47.226 [8531] dbg: channel: current version is 1720996, new 
version is 1720996, skipping channel
Jan  4 13:55:47.226 [8531] dbg: dia

Re: sa-update not updating the rules

[Reindl Harald]

Am 04.01.2016 um 22:18 schrieb Muthu N.C:

I am using the version 3.4.1 spamassassin. I am running sa-update to
update the rules. The rules stopped updating after Dec 21st. Below is
the output when running with debug mode..Any help on getting the latest
update of the rulls will be helpful.


when there is nothing then you get nothing

02-Dez-2015 01:02:53: SpamAssassin: Update processed successfully
03-Dez-2015 00:37:51: SpamAssassin: Update processed successfully
04-Dez-2015 00:56:46: SpamAssassin: Update processed successfully
05-Dez-2015 00:00:16: SpamAssassin: Update processed successfully
06-Dez-2015 00:45:06: SpamAssassin: No update available
07-Dez-2015 00:19:04: SpamAssassin: No update available
08-Dez-2015 00:14:33: SpamAssassin: No update available
09-Dez-2015 00:15:58: SpamAssassin: No update available
10-Dez-2015 01:09:43: SpamAssassin: No update available
11-Dez-2015 01:20:40: SpamAssassin: No update available
12-Dez-2015 01:13:00: SpamAssassin: No update available
13-Dez-2015 00:49:06: SpamAssassin: No update available
14-Dez-2015 01:04:57: SpamAssassin: No update available
15-Dez-2015 01:09:07: SpamAssassin: No update available
16-Dez-2015 00:37:36: SpamAssassin: No update available
17-Dez-2015 00:27:17: SpamAssassin: No update available
18-Dez-2015 00:38:14: SpamAssassin: No update available
19-Dez-2015 01:12:45: SpamAssassin: No update available
20-Dez-2015 00:21:46: SpamAssassin: No update available
21-Dez-2015 00:28:33: SpamAssassin: No update available
22-Dez-2015 00:10:51: SpamAssassin: Update processed successfully
23-Dez-2015 00:59:08: SpamAssassin: No update available
24-Dez-2015 00:17:03: SpamAssassin: No update available
25-Dez-2015 00:50:35: SpamAssassin: No update available
26-Dez-2015 00:20:16: SpamAssassin: No update available
27-Dez-2015 00:52:26: SpamAssassin: No update available
28-Dez-2015 00:25:01: SpamAssassin: No update available
29-Dez-2015 01:51:52: SpamAssassin: No update available
30-Dez-2015 00:29:27: SpamAssassin: No update available
31-Dez-2015 01:11:06: SpamAssassin: No update available
01-Jan-2016 00:24:50: SpamAssassin: No update available
02-Jan-2016 00:22:49: SpamAssassin: No update available
03-Jan-2016 00:32:25: SpamAssassin: No update available
04-Jan-2016 00:03:32: SpamAssassin: No update available



signature.asc
Description: OpenPGP digital signature

Re: sa-update not updating?

[Kevin A. McGrail]

On 2/7/2015 6:40 PM, David Dodell wrote:

My sa-update has been working well for month … updating at 5 am local time with 
new rules.

Starting last week, I haven’t seen an update, my sa-update ends up with exiting 
with level 1, showing that the update server is at version 1655961 and no new 
update is needed.

But it looks from the wiki that the updates are at 1658033 

Since I am playing a network administrator on TV, and didn’t stay at a Holiday 
Inn Express … am I missing something … the amount of spam getting through has 
increased since last week.

Is there a way to “force” an update to the latest rules, ignoring what I have 
on my server to get me back in sync?

Suggestions / help?

Thanks

David


Rules are not always published every night.  The publishing of rules is 
driven by an automated process I'll refer to as RuleQA.


The RuleQA requires a certain amount of spam and ham corpora checks from 
masscheck submitters.  Unfortunately, we have been missing the threshold 
for the past week or so and it might take another week to sort things out.


There is nothing wrong with your server however there are rules still 
generated for the project just not published because of the way the 
ruleqa didn't meet the threshold.



You might find adding our ruleset is helpful in the meantime: 
http://www.pccc.com/downloads/SpamAssassin/contrib/KAM.cf


Regards,
KAM

Re: sa-update NOT updating.

[Ben]

At the ASF, there is an infrastructure team that manages those type of
issues.  They work hard and do a lot of good but unfortunately, there
was a disconnect back in 2009 and a backup request was not implemented
correctly.



An untested backup is not a backup.  Some people only ever seem to learn 
that the hard way.


To be honest, given the popularity of SA and the relative importance of 
the sa-update service it's astonishing that such a SPOF with such a lax 
management routine was allowed to occur.

Re: sa-update NOT updating.

[John Hardin]

On Mon, 16 Jun 2014, francis picabia wrote:


If this is open source, why not take advantage of all of the repositories
available for this?  Git?  Sourceforge?  Mirrors?  The problem isn't merely
the lack of a backup, but a single point of failure waiting to happen.


The point of failure isn't simply a set of files, it's a processing 
resource.


Something like a VM snapshot that could be easily restored (i.e. on an 
Amazon cloud server, say) to get a working environment would be a good way 
to back up centralized part of the masscheck infrastructure.


Kevin, is this running on a VM now, such that this is an option?

--
 John Hardin KA7OHZhttp://www.impsec.org/~jhardin/
 jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org
 key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
---
  Microsoft is not a standards body.
---
 2 days until SWMBO's Birthday

Re: sa-update NOT updating.

[Axb]

On 06/16/2014 08:39 PM, francis picabia wrote:

If this is open source, why not take advantage of all of the repositories
available for this?  Git?  Sourceforge?  Mirrors?  The problem isn't merely
the lack of a backup, but a single point of failure waiting to happen.
When something goes wrong with kernel.org or the like, it isn't backup
tapes that get them online again quickly.  I don't know enough about it,
but I know the general principle that if you have a problem you're likely
not the first to encounter it, and you usually don' t need to invent a
solution, but look into how it has been solved elsewhere.


This not about where to store code...

This about a system that does all the rule score manipulation, prepares 
updates, etc, etc, etc

Software repositories don't handle this.
There is no similar processing going on elsewhere.

Re: sa-update NOT updating.

[Kevin A. McGrail]

On 6/16/2014 2:39 PM, francis picabia wrote:
If this is open source, why not take advantage of all of the 
repositories available for this?  Git?  Sourceforge? Mirrors?  The 
problem isn't merely the lack of a backup, but a single point of 
failure waiting to happen.  When something goes wrong with kernel.org 
 or the like, it isn't backup tapes that get them 
online again quickly.  I don't know enough about it, but I know the 
general principle that if you have a problem you're likely not the 
first to encounter it, and you usually don' t need to invent a 
solution, but look into how it has been solved elsewhere.
At the ASF, there is an infrastructure team that manages those type of 
issues.  They work hard and do a lot of good but unfortunately, there 
was a disconnect back in 2009 and a backup request was not implemented 
correctly.


So this is less about inventing a wheel and more about making sure that 
we have air in the spare tire...


regards,
KAM

Re: sa-update NOT updating.

[francis picabia]

On Mon, Jun 16, 2014 at 12:36 PM, Kevin A. McGrail 
wrote:

> On 6/16/2014 9:49 AM, Joe Quinn wrote:
>
>> On 6/16/2014 9:42 AM, Dave Pooser wrote:
>>
>>> On 5/30/14 11:11 AM, "Kevin A. McGrail"  wrote:
>>>
>>>  Good time for an update to the users list about the issue.  The box that
 processed the updates at the ASF collo failed catastrophically during a
 power surge that took down some other boxes as ell. Unfortunately, while
 the project requested backups in 2009, they were not implemented.

>>> Now that the update box is back online (and thanks for all your hard work
>>> on that! Systems archaeology is no fun at all), is there anything useful
>>> the community can do to help prevent another such catastrophe? I'd be
>>> willing to contribute hardware and/or VM space at $WORKPLACE for an
>>> offsite replica as long as we wouldn't need to sync more than 2-4GB/day
>>> after the initial setup completed.
>>>
>>
>> If you have access to any SA boxes, make sure they have a scheduled
>> backup (and make sure the backup works and has all important data!). If any
>> systems do not have backups, report it to the appropriate list.
>>
>> Also make sure every task the box is designed to handle is appropriately
>> documented, including user accounts required, libraries required and their
>> versions, what crontabs should be, etc.
>>
> I think Joe's answer is correct but at the same time doesn't answer the
> question of what the community at large can do to help.
>
> First, the overall takeaway for me is that documentation is important.
>  This was a hard task when it was just a box failure. When it became a box
> failure with missing backups and large documentation issues, it effectively
> became a personal mission to get the box working.  A little documentation
> on things went a long way for me and especially in the OS world, people
> burnout or go on to other projects so it's helpful if you try and document.
>
> Second, to answer your question less philosophically, from the community
> we always need:
>
> - Masscheckers - You run code nightly and automated against a hand sorted
> spam/ham corpora to improve our rule scoring.  Once you get it setup and
> get good, sorted email, the system is very automated.
>
> - Rule writers - Spam evolves and we need people to write rules.  If you
> like balancing your checkbook, doing SoDoKu, see patterns in gibberish,
> this might be perfect for you.  And what I love doing is evolving the rule
> writing from manual to automated processing.  It's quite a science really!
>
> - Coders - The life blood of a project really.  If you want to help write
> code, become a committer and help drive this project on the PMC, speak up!
>
> - Testers - People who will use trunk on production systems and give
> constructive feedback on real-world mail flow.  NOTE: trunk is usually in
> good shape and runs on many of the committers systems. Because of the way
> the system is plugin based, the experimental stuff is usually not enabled
> by default.
>
> - RBL Stuff - I'm also still working with the ASF to see if we can run a
> distributed RBL under the projects Umbrella so stay tuned on that...
>
>
If this is open source, why not take advantage of all of the repositories
available for this?  Git?  Sourceforge?  Mirrors?  The problem isn't merely
the lack of a backup, but a single point of failure waiting to happen.
When something goes wrong with kernel.org or the like, it isn't backup
tapes that get them online again quickly.  I don't know enough about it,
but I know the general principle that if you have a problem you're likely
not the first to encounter it, and you usually don' t need to invent a
solution, but look into how it has been solved elsewhere.

Re: sa-update NOT updating.

[Kevin A. McGrail]

On 6/16/2014 9:49 AM, Joe Quinn wrote:

On 6/16/2014 9:42 AM, Dave Pooser wrote:

On 5/30/14 11:11 AM, "Kevin A. McGrail"  wrote:

Good time for an update to the users list about the issue.  The box 
that

processed the updates at the ASF collo failed catastrophically during a
power surge that took down some other boxes as ell. Unfortunately, 
while

the project requested backups in 2009, they were not implemented.
Now that the update box is back online (and thanks for all your hard 
work

on that! Systems archaeology is no fun at all), is there anything useful
the community can do to help prevent another such catastrophe? I'd be
willing to contribute hardware and/or VM space at $WORKPLACE for an
offsite replica as long as we wouldn't need to sync more than 2-4GB/day
after the initial setup completed.


If you have access to any SA boxes, make sure they have a scheduled 
backup (and make sure the backup works and has all important data!). 
If any systems do not have backups, report it to the appropriate list.


Also make sure every task the box is designed to handle is 
appropriately documented, including user accounts required, libraries 
required and their versions, what crontabs should be, etc.
I think Joe's answer is correct but at the same time doesn't answer the 
question of what the community at large can do to help.


First, the overall takeaway for me is that documentation is important.  
This was a hard task when it was just a box failure. When it became a 
box failure with missing backups and large documentation issues, it 
effectively became a personal mission to get the box working.  A little 
documentation on things went a long way for me and especially in the OS 
world, people burnout or go on to other projects so it's helpful if you 
try and document.


Second, to answer your question less philosophically, from the community 
we always need:


- Masscheckers - You run code nightly and automated against a hand 
sorted spam/ham corpora to improve our rule scoring.  Once you get it 
setup and get good, sorted email, the system is very automated.


- Rule writers - Spam evolves and we need people to write rules.  If you 
like balancing your checkbook, doing SoDoKu, see patterns in gibberish, 
this might be perfect for you.  And what I love doing is evolving the 
rule writing from manual to automated processing.  It's quite a science 
really!


- Coders - The life blood of a project really.  If you want to help 
write code, become a committer and help drive this project on the PMC, 
speak up!


- Testers - People who will use trunk on production systems and give 
constructive feedback on real-world mail flow.  NOTE: trunk is usually 
in good shape and runs on many of the committers systems. Because of the 
way the system is plugin based, the experimental stuff is usually not 
enabled by default.


- RBL Stuff - I'm also still working with the ASF to see if we can run a 
distributed RBL under the projects Umbrella so stay tuned on that...


Regards,
KAM

Re: sa-update NOT updating.

[Dave Pooser]

On 5/30/14 11:11 AM, "Kevin A. McGrail"  wrote:

>Good time for an update to the users list about the issue.  The box that
>processed the updates at the ASF collo failed catastrophically during a
>power surge that took down some other boxes as ell. Unfortunately, while
>the project requested backups in 2009, they were not implemented.

Now that the update box is back online (and thanks for all your hard work
on that! Systems archaeology is no fun at all), is there anything useful
the community can do to help prevent another such catastrophe? I'd be
willing to contribute hardware and/or VM space at $WORKPLACE for an
offsite replica as long as we wouldn't need to sync more than 2-4GB/day
after the initial setup completed.
-- 
Dave Pooser
Cat-Herder-in-Chief, Pooserville.com

Re: sa-update NOT updating.

[Joe Quinn]

On 6/16/2014 9:42 AM, Dave Pooser wrote:

On 5/30/14 11:11 AM, "Kevin A. McGrail"  wrote:


Good time for an update to the users list about the issue.  The box that
processed the updates at the ASF collo failed catastrophically during a
power surge that took down some other boxes as ell. Unfortunately, while
the project requested backups in 2009, they were not implemented.

Now that the update box is back online (and thanks for all your hard work
on that! Systems archaeology is no fun at all), is there anything useful
the community can do to help prevent another such catastrophe? I'd be
willing to contribute hardware and/or VM space at $WORKPLACE for an
offsite replica as long as we wouldn't need to sync more than 2-4GB/day
after the initial setup completed.


If you have access to any SA boxes, make sure they have a scheduled 
backup (and make sure the backup works and has all important data!). If 
any systems do not have backups, report it to the appropriate list.


Also make sure every task the box is designed to handle is appropriately 
documented, including user accounts required, libraries required and 
their versions, what crontabs should be, etc.

Re: sa-update NOT updating.

[Kevin A. McGrail]

On 5/27/2014 3:47 PM, John Goubeaux wrote:

Thanks guys,

Yes, I was aware that an exit code of   "1" IS normal when No New 
updates are available, But I assumed that the fact that this was going 
on for so long might indicate another problem was occurring.
Good time for an update to the users list about the issue.  The box that 
processed the updates at the ASF collo failed catastrophically during a 
power surge that took down some other boxes as ell. Unfortunately, while 
the project requested backups in 2009, they were not implemented.


Since that crash, I've recovered a lot of the data and rebuilt several 
of the services from the data recovery, rsync backups and svn data.  I 
also had the new box increased by 100GB in diskspace thanks to Jan 
Iverson with Infra because I was spending too much time manipulating 
data due to low space.


Yesterday, I spent some time as well and Joes4 from Infra agreed to try 
to recovered the crontab/spools today though he is not hopeful. 
Otherwise, luckily I have cron logs and I think I've identified most of 
the scripts that run from cron.


So at this point, I will soon have exhausted all of the attempts to 
recover without going to the next phase which is to try and reverse 
engineer the cron jobs.  The hardest part is that there are multiple 
iterations of the various pieces of the masscheck system that have been 
put in place so I have to figure out in some cases, which one is the 
right piece.


And at the same time, I've been properly documenting the changes to the 
underlying system so should I get hit by a bus, the system can be 
rebuilt without me.


Apparently the sought.rules.yerp.org  channel is also not being 
regularly updated either ?
Sought is technically not a project ruleset but I think I now have 
access to all the boxes to get it running again.  Alex Broens has 
offered to help so I hope to get him that info soon.  It's a second 
priority after the rebuild of the zones box.


Are there any other recommended  rule channels to use ?


I would recommend this rule set though I do not publish it as a channel 
though some (thanks Gushi) have attempted to help me do so: 
http://www.pccc.com/downloads/SpamAssassin/contrib/KAM.cf


Regards,
KAM

Re: sa-update NOT updating.

[John Goubeaux]

Thanks guys,

Yes, I was aware that an exit code of   "1" IS 
normal when No New updates are available, But I 
assumed that the fact that this was going on for 
so long might indicate another problem was 
occurring.


Apparently the sought.rules.yerp.org  channel is 
also not being regularly updated either ?


Are there any other recommended  rule channels to use ?

-john







At 9:08 PM +0200 5/27/14, Karsten Bräckelmann wrote:

On Tue, 2014-05-27 at 14:22 -0400, Kevin A. McGrail wrote:

 We are not currently publishing updates.  I will try and get another
 push done on that box today.

 On 5/27/2014 2:09 PM, John Goubeaux wrote:
 > Can anyone shed some light on what might be happening  -or not
 > happening - with  sa-update and my install, I am continually getting
 > an "exiting with code 1" when sa-update is run.  Full  -D output
 > pasted at the very bottom.


An exit code of 1 does not indicate an error. It merely means no fresh
updates were available, your rule-set is up to date.

See man sa-update, section Exit Codes.


--
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}



--
John Goubeaux
Systems Administrator
Gevirtz Graduate School of Education
UC Santa Barbara
Education 4203C
805 893-8190

Re: sa-update NOT updating.

[Karsten Bräckelmann]

On Tue, 2014-05-27 at 14:22 -0400, Kevin A. McGrail wrote:
> We are not currently publishing updates.  I will try and get another
> push done on that box today. 
> 
> On 5/27/2014 2:09 PM, John Goubeaux wrote:
> > Can anyone shed some light on what might be happening  -or not
> > happening - with  sa-update and my install, I am continually getting
> > an "exiting with code 1" when sa-update is run.  Full  -D output
> > pasted at the very bottom.

An exit code of 1 does not indicate an error. It merely means no fresh
updates were available, your rule-set is up to date.

See man sa-update, section Exit Codes.


-- 
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}

Re: sa-update NOT updating.

[Kevin A. McGrail]

We are not currently publishing updates.  I will try and get another 
push done on that box today.


On 5/27/2014 2:09 PM, John Goubeaux wrote:
Can anyone shed some light on what might be happening  -or not 
happening -   with  sa-update and my install, I am continually getting an
"exiting with code 1" when sa-update is run.  Full   -D output pasted 
at the very bottom.



/usr/local/bin> ./spamassassin -V
SpamAssassin version 3.4.0
  running on Perl version 5.8.8


Since I did the upgrade to 3.4.0, at which time the rules WERE 
updated,  I have NOT seen a successful rule update since.


/usr/local/bin> /usr/local/bin/sa-update --nogpg -D --channel 
sought.rules.yerp.org --channel updates.spamassassin.org



Rules directory looks good:


/usr/local/bin> ls -la /var/lib/spamassassin/3.004*

drwxr-xr-x   2 root root 512 May  6 13:45 
sought_rules_yerp_org
-rw-r--r--   1 root root 123 May  6 13:45 
sought_rules_yerp_org.cf
drwxr-xr-x   2 root root2048 May  6 13:45 
updates_spamassassin_org
-rw-r--r--   1 root root2695 May  6 13:45 
updates_spamassassin_org.cf




/usr/local/bin> /usr/local/bin/sa-update --nogpg -D --channel 
sought.rules.yerp.org --channel updates.spamassassin.org

May 27 11:02:03.911 [16964] dbg: logger: adding facilities: all
May 27 11:02:03.912 [16964] dbg: logger: logging level is DBG
May 27 11:02:03.912 [16964] dbg: generic: SpamAssassin version 3.4.0
May 27 11:02:03.912 [16964] dbg: generic: Perl 5.008008, 
PREFIX=/usr/local, DEF_RULES_DIR=/usr/local/share/spamassassin, 
LOCAL_RULES_DIR=/etc/mail/spamassassin, 
LOCAL_STATE_DIR=/var/lib/spamassassin

May 27 11:02:03.912 [16964] dbg: config: timing enabled
May 27 11:02:03.913 [16964] dbg: config: score set 0 chosen.
May 27 11:02:03.919 [16964] dbg: generic: sa-update version svn1475932
May 27 11:02:03.919 [16964] dbg: generic: using update directory: 
/var/lib/spamassassin/3.004000

May 27 11:02:04.148 [16964] dbg: diag: perl platform: 5.008008 solaris
May 27 11:02:04.148 [16964] dbg: diag: [...] module installed: 
Digest::SHA1, version 2.11
May 27 11:02:04.149 [16964] dbg: diag: [...] module installed: 
HTML::Parser, version 3.56
May 27 11:02:04.149 [16964] dbg: diag: [...] module installed: 
Net::DNS, version 0.72
May 27 11:02:04.149 [16964] dbg: diag: [...] module installed: 
NetAddr::IP, version 4.073
May 27 11:02:04.149 [16964] dbg: diag: [...] module installed: 
Time::HiRes, version 1.86
May 27 11:02:04.149 [16964] dbg: diag: [...] module installed: 
Archive::Tar, version 1.32
May 27 11:02:04.149 [16964] dbg: diag: [...] module installed: 
IO::Zlib, version 1.05
May 27 11:02:04.149 [16964] dbg: diag: [...] module installed: 
Digest::SHA1, version 2.11
May 27 11:02:04.149 [16964] dbg: diag: [...] module installed: 
MIME::Base64, version 3.07
May 27 11:02:04.149 [16964] dbg: diag: [...] module installed: 
DB_File, version 1.815
May 27 11:02:04.149 [16964] dbg: diag: [...] module installed: 
Net::SMTP, version 2.31
May 27 11:02:04.149 [16964] dbg: diag: [...] module installed: 
Mail::SPF, version v2.009
May 27 11:02:04.149 [16964] dbg: diag: [...] module installed: 
Geo::IP, version 1.43
May 27 11:02:04.149 [16964] dbg: diag: [...] module installed: 
Razor2::Client::Agent, version 2.84
May 27 11:02:04.149 [16964] dbg: diag: [...] module not installed: 
IO::Socket::IP ('require' failed)
May 27 11:02:04.149 [16964] dbg: diag: [...] module installed: 
IO::Socket::INET6, version 2.71
May 27 11:02:04.149 [16964] dbg: diag: [...] module installed: 
IO::Socket::SSL, version 1.07
May 27 11:02:04.149 [16964] dbg: diag: [...] module installed: 
Compress::Zlib, version 2.004
May 27 11:02:04.149 [16964] dbg: diag: [...] module installed: 
Mail::DKIM, version 0.4
May 27 11:02:04.149 [16964] dbg: diag: [...] module installed: DBI, 
version 1.56
May 27 11:02:04.149 [16964] dbg: diag: [...] module installed: 
Getopt::Long, version 2.35
May 27 11:02:04.149 [16964] dbg: diag: [...] module installed: 
LWP::UserAgent, version 2.033
May 27 11:02:04.149 [16964] dbg: diag: [...] module installed: 
HTTP::Date, version 1.47
May 27 11:02:04.149 [16964] dbg: diag: [...] module installed: 
Encode::Detect, version 1.01
May 27 11:02:04.149 [16964] dbg: diag: [...] module installed: 
Net::Patricia, version 1.22
May 27 11:02:04.151 [16964] dbg: channel: attempting channel 
sought.rules.yerp.org
May 27 11:02:04.151 [16964] dbg: channel: using existing directory 
/var/lib/spamassassin/3.004000/sought_rules_yerp_org
May 27 11:02:04.151 [16964] dbg: channel: channel cf file 
/var/lib/spamassassin/3.004000/sought_rules_yerp_org.cf
May 27 11:02:04.151 [16964] dbg: channel: channel pre file 
/var/lib/spamassassin/3.004000/sought_rules_yerp_org.pre
May 27 11:02:04.159 [16964] dbg: channel: metadata version = 
3402014020421, from file 
/var/lib/spamassassin/3.004000/sought_rules_yerp_org.cf
May 27 11:02:04.189 [16964] dbg: dns: 0.4.3.sought.rules.yerp.org => 
3402014020421, parsed as 3402014020421
May 27 11:02:04.189 [16964] dbg

Re: sa-update not updating since March 30.

[John Hardin]

On Mon, 1 Jun 2009, Ernie Dunbar wrote:


John Hardin wrote:


On Mon, 1 Jun 2009, Ernie Dunbar wrote:


We have a cron job that runs every day to update the spamassassin rules,
but there have been no new updates since March 30.


That's because there haven't been any updates recently. There's no firm
schedule for releases of updates.


Ah. That certainly explains why we're getting massive amounts of spam.

How would I go about contributing to that end?


Read up in the SA wiki on how to become a committer. You need that level 
of access to submit rules for consideration even if you're not going to be 
hacking the SA code itself. Barring that, posting rules to the users list 
for discussion may lead to them being adopted into the base rules.


I'm in the process of becoming a committer for this reason myself. One 
thing I intend to do is get some newer rules into the 3.2 tree, as the 
"real" devs are focusing on 3.3


--
 John Hardin KA7OHZhttp://www.impsec.org/~jhardin/
 jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org
 key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
---
  Of the twenty-two civilizations that have appeared in history,
  nineteen of them collapsed when they reached the moral state the
  United States is in now.  -- Arnold Toynbee
---
 5 days until the 65th anniversary of D-Day

Re: sa-update not updating since March 30.

[Ernie Dunbar]

John Hardin wrote:
> 
> On Mon, 1 Jun 2009, Ernie Dunbar wrote:
> 
>> We have a cron job that runs every day to update the spamassassin rules, 
>> but there have been no new updates since March 30.
> 
> That's because there haven't been any updates recently. There's no firm 
> schedule for releases of updates.
> 

Ah. That certainly explains why we're getting massive amounts of spam.

How would I go about contributing to that end?
-- 
View this message in context: 
http://www.nabble.com/sa-update-not-updating-since-March-30.-tp23819671p23820187.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.

Re: sa-update not updating since March 30.

[McDonald, Dan]

On Mon, 2009-06-01 at 11:26 -0700, Ernie Dunbar wrote:
> We have a cron job that runs every day to update the spamassassin rules, but
> there have been no new updates since March 30.

Correct.  updates_spamassassin_org has not been updated since March 30.
I have seen updates on 90_sare_freemail_cf_sare_sa-update_dostech_net
(May 11), 90_2tld_cf_sare_sa-update_dostech_net (May 24th), and
sought_rules_yerp_org (today).


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


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

Re: sa-update not updating since March 30.

[John Hardin]

On Mon, 1 Jun 2009, Ernie Dunbar wrote:

We have a cron job that runs every day to update the spamassassin rules, 
but there have been no new updates since March 30.


That's because there haven't been any updates recently. There's no firm 
schedule for releases of updates.


--
 John Hardin KA7OHZhttp://www.impsec.org/~jhardin/
 jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org
 key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
---
  Government cannot grant rights. Government can only limit, infringe
  or suppress rights.
---
 5 days until the 65th anniversary of D-Day