updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-11-06 Thread noreply
3.3.3.updates (TXT) -> \"1814390\" File /usr/local/bin/updateDNS.disabled exists, not updating DNS.

Re: Fwd: Cron <root@sa-vm1> svn update /var/www/automc.spamassassin.org/updates > /dev/null

2017-11-06 Thread Kevin A. McGrail
Ty. Regards, KAM On November 6, 2017 3:56:32 AM PST, Dave Jones wrote: >On 11/06/2017 05:53 AM, Kevin A. McGrail wrote: >> Neat >> Regards, >> KAM >> >> > >That seemed to be a temporary problem with DNS or SVN. I was able to >run the same command just now without a

Re: Fwd: Cron <root@sa-vm1> svn update /var/www/automc.spamassassin.org/updates > /dev/null

2017-11-06 Thread Dave Jones
On 11/06/2017 05:53 AM, Kevin A. McGrail wrote: Neat Regards, KAM That seemed to be a temporary problem with DNS or SVN. I was able to run the same command just now without a problem. Dave Original Message From: r...@sa-vm1.apache.org Sent: November 6, 2017

Cron <root@sa-vm1> svn update /var/www/automc.spamassassin.org/updates > /dev/null

2017-11-06 Thread Cron Daemon
svn: E670005: No address associated with hostname

72_scores.cf compared to the one from march 15

2017-11-06 Thread Merijn van den Kroonenberg
Hi, When I compare the current 72_scores.cf with the one from march 15 I can see we are getting closer and closer. The march one has 144 lines and the current one has 108. When looking at the rules which are missing, then one case stands out clearly: All rules in the march version with a

Cron <automc@sa-vm1> ~/svn/trunk/build/mkupdates/run_nightly | /usr/bin/tee /var/www/automc.spamassassin.org/mkupdates/mkupdates.txt

2017-11-06 Thread Cron Daemon
+ promote_active_rules + pwd /usr/local/spamassassin/automc/svn/trunk + /usr/bin/perl build/mkupdates/listpromotable HTTP get: http://ruleqa.spamassassin.org/1-days-ago?xml=1 HTTP get: http://ruleqa.spamassassin.org/2-days-ago?xml=1 day 2 contains a --net mass-check! offsetting by an extra day Use