updateDNS.sh on sa-vm1.apache.org - DNS updates disabled
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
Ty. Regards, KAM On November 6, 2017 3:56:32 AM PST, Dave Joneswrote: >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 6:30:07 AM EST >> To: sysadmins@spamassassin.apache.org >> Subject: Cron svn update >/var/www/automc.spamassassin.org/updates > /dev/null >> >> svn: E670005: No address associated with hostname >>
Re: Fwd: Cron <root@sa-vm1> svn update /var/www/automc.spamassassin.org/updates > /dev/null
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 6:30:07 AM EST To: sysadmins@spamassassin.apache.org Subject: Cronsvn update /var/www/automc.spamassassin.org/updates > /dev/null svn: E670005: No address associated with hostname
Cron <root@sa-vm1> svn update /var/www/automc.spamassassin.org/updates > /dev/null
svn: E670005: No address associated with hostname
72_scores.cf compared to the one from march 15
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 score like this: 1.000 1.000 1.000 1.000 Are missing from our current 72_scores.cf [edit: they all seem to be in active.list with a tflags publish] I will see if I can find where they get lost ;) One other rule which is still missing is RP_MATCHES_RCVD, which i could imagine being used in custom meta rules. So I compile a list of all rules in the March 72_scores.cf which are not in our current: AC_SPAMMY_URI_PATTERNS1 AC_SPAMMY_URI_PATTERNS10 AC_SPAMMY_URI_PATTERNS11 AC_SPAMMY_URI_PATTERNS12 AC_SPAMMY_URI_PATTERNS2 AC_SPAMMY_URI_PATTERNS3 AC_SPAMMY_URI_PATTERNS4 AC_SPAMMY_URI_PATTERNS8 AC_SPAMMY_URI_PATTERNS9 AXB_XMAILER_MIMEOLE_OL_1ECD5 AXB_XM_FORGED_OL2600 BODY_EMPTY CANT_SEE_AD CN_B2B_SPAMMER COMMENT_GIBBERISH ENCRYPTED_MESSAGE FORM_LOW_CONTRAST FOUND_YOU FREEMAIL_DOC_PDF_BCC FROM_WORDY_SHORT FSL_HELO_BARE_IP_2 GOOGLE_DOCS_PHISH GOOGLE_DOCS_PHISH_MANY GOOG_MALWARE_DNLD HDRS_LCASE HEXHASH_WORD HK_SCAM_N15 HTML_OFF_PAGE LIST_PRTL_PUMPDUMP LIST_PRTL_SAME_USER LOTTO_AGENT LOTTO_DEPT LUCRATIVE MIME_NO_TEXT MONEY_LOTTERY MSGID_NOFQDN1 MSM_PRIO_REPTO PHP_NOVER_MUA PHP_ORIG_SCRIPT PHP_SCRIPT_MUA PP_TOO_MUCH_UNICODE02 PP_TOO_MUCH_UNICODE05 PUMPDUMP PUMPDUMP_MULTI RAND_HEADER_MANY RP_MATCHES_RCVD SHARE_50_50 SPOOFED_FREEM_REPTO_CHN STOCK_LOW_CONTRAST STOCK_TIP SYSADMIN TO_NO_BRKTS_PCNT TW_GIBBERISH_MANY UC_GIBBERISH_OBFU URI_DATA URI_OPTOUT_3LD XPRIO_SHORT_SUBJ Which are 57 rules, more than the difference in rulecount. This means there are also many rules in our current 72_scores.cf which are not in the march version. Can someone explain to me why or in which cases rules are added or removed from the 72_scores.cf? What I already know: 1) during rule promotion rules are added/removed frome active.list which in turn will add/remove them from 72_scores.cf A few from the above list of rules can be tracked to active.list changes (rule promotions) between then and now. But most are still in active.list. Cheers, Merijn
Cron <automc@sa-vm1> ~/svn/trunk/build/mkupdates/run_nightly | /usr/bin/tee /var/www/automc.spamassassin.org/mkupdates/mkupdates.txt
+ 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 of "goto" to jump into a construct is deprecated at build/mkupdates/listpromotable line 85. HTTP get: http://ruleqa.spamassassin.org/3-days-ago?xml=1 HTTP get: http://ruleqa.spamassassin.org/4-days-ago?xml=1 no 'mcviewing', 'mcsubmitters' microformats on day 3 URL: http://ruleqa.spamassassin.org/4-days-ago?xml=1 + exit 25