Re: SA-Update not updating DB

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

Re: SA-Update not updating DB

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

Re: SA-Update not updating DB

> 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

Re: SA-Update not updating DB

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

Re: SA-Update not updating DB

+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

Re: SA-Update not updating DB

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

Re: SA-Update not updating DB

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

Re: SA-Update not updating DB

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.

Re: SA-Update not updating DB

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

Re: SA-Update not updating DB

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

Re: SA-Update not updating DB

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:

Re: SA-Update not updating DB

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

Re: SA-Update not updating DB

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

Re: SA-Update not updating DB

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

Re: SA-Update not updating DB

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

Re: SA-Update not updating DB

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

Re: SA-Update not updating DB

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

Re: SA-Update not updating DB

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

Re: SA-Update not updating DB

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

SA-Update not updating DB

Hi Everyone, 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. Here is the command, and output I am getting. [root@mail-master 3.004001]# sa-update -v -D

Re: sa-update not updating the rules

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

Re: sa-update not updating the rules

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

Re: sa-update not updating the rules

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

sa-update not updating the rules

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:

Re: sa-update not updating the rules

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.

Re: sa-update not updating the rules

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.

Re: sa-update not updating the rules

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.

Re: sa-update not updating the rules

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

Re: sa-update not updating the rules

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.

Re: sa-update not updating the rules

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

Re: sa-update not updating the rules

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

sa-update not updating?

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

Re: sa-update not updating?

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

Re: sa-update NOT updating.

On 6/16/2014 9:42 AM, Dave Pooser wrote: On 5/30/14 11:11 AM, Kevin A. McGrail kmcgr...@pccc.com 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

Re: sa-update NOT updating.

On 5/30/14 11:11 AM, Kevin A. McGrail kmcgr...@pccc.com 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

Re: sa-update NOT updating.

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 kmcgr...@pccc.com 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

Re: sa-update NOT updating.

On Mon, Jun 16, 2014 at 12:36 PM, Kevin A. McGrail kmcgr...@pccc.com 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 kmcgr...@pccc.com wrote: Good time for an update to the users list about the issue. The box

Re: sa-update NOT updating.

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

Re: sa-update NOT updating.

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

Re: sa-update NOT updating.

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

Re: sa-update NOT updating.

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

Re: sa-update NOT updating.

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

sa-update NOT updating.

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

Re: sa-update NOT updating.

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

Re: sa-update NOT updating.

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

Re: sa-update NOT updating.

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

sa-update not updating since March 30.

] dbg: dns: 5.2.3.updates.spamassassin.org = 759778, parsed as 759778 [24667] dbg: channel: current version is 759778, new version is 759778, skipping channel [24667] dbg: diag: updates complete, exiting with code 1 -- View this message in context: http://www.nabble.com/sa-update-not-updating-since

Re: sa-update not updating since March 30.

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

Re: sa-update not updating since March 30.

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

Re: sa-update not updating since March 30.

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

Re: sa-update not updating since March 30.

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