Re: Are we ready in DNS for 3.4.5 release?

2021-03-24 Thread Kevin A. McGrail

Hi Sidney,

So if you ever need, there is more information here: 
https://cwiki.apache.org/confluence/display/SPAMASSASSIN/InfraNotes2020


Yes, there is a 3.4.5 record

5.4.3.updates.spamassassin.org. 3599 IN CNAME 
3.3.3.updates.spamassassin.org.


Regards,
KAM

On 3/24/2021 1:23 PM, Sidney Markowitz wrote:
Here's a quote from build/README which says my next step in the 
release process is to ask you all if you have to do whatever this says 
has to be done.

So I'm asking...


Confirm with SpamAssassin SysAdmins group that we are ready in DNS for
  masscheck and rule updates for the next version

  For many years all releases since 3.3.3 use the same ruleset.
    3.4.2 already has a cname for this.
    3.3.2 and before are set to a static ruleset.

  We have been good on using version specific and plugin conditions to
  allow one ruleset to rule them all.

  Since we plan to release rules that continue to be version compatible
  back to 3.3.3, only a CNAME is needed for newer releases to point at
  3.3.3.


--
Kevin A. McGrail
kmcgr...@apache.org

Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171



Are we ready in DNS for 3.4.5 release?

2021-03-24 Thread Sidney Markowitz

Here's a quote from build/README which says my next step in the release process 
is to ask you all if you have to do whatever this says has to be done.
So I'm asking...


Confirm with SpamAssassin SysAdmins group that we are ready in DNS for
  masscheck and rule updates for the next version

  For many years all releases since 3.3.3 use the same ruleset.
3.4.2 already has a cname for this.
3.3.2 and before are set to a static ruleset.

  We have been good on using version specific and plugin conditions to
  allow one ruleset to rule them all.

  Since we plan to release rules that continue to be version compatible
  back to 3.3.3, only a CNAME is needed for newer releases to point at
  3.3.3.


checkSAupdateMirrors.sh on sa-vm.apache.org - 1 mirror DOWN, 0 mirrors STALE

2021-03-24 Thread automc
Fetching sa-update URLs from http://spamassassin.apache.org/updates/MIRRORED.BY

http://sa-update.dnswl.org/ (116.203.4.105): UP (CURRENT)

http://www.sa-update.pccc.com/ (69.171.29.42): DOWN

http://sa-update.space-pro.be/ (176.28.55.20): UP (CURRENT)

http://sa-update.ena.com/ (96.5.1.5): UP (CURRENT)

http://sa-update.ena.com/ (96.4.1.5): UP (CURRENT)

http://sa-update.razx.cloud/ (172.67.170.149): UP (CURRENT)

http://sa-update.razx.cloud/ (104.21.71.133): UP (CURRENT)

http://sa-update.fossies.org/ (144.76.163.196): UP (CURRENT)

http://sa-update.verein-clean.net/ (148.251.212.58): UP (CURRENT)

http://sa-update.verein-clean.net/ (37.252.120.157): UP (CURRENT)

http://sa-update.verein-clean.net/ (37.252.124.130): UP (CURRENT)

http://sa-update-asf.snb.it/ (151.80.178.91): UP (CURRENT)

http://sa-update.spamassassin.org/ (64.142.56.146): UP (CURRENT)


Cron ~/svn/trunk/build/mkupdates/run_nightly | /usr/bin/tee /var/www/automc.spamassassin.org/mkupdates/mkupdates.txt

2021-03-24 Thread Cron Daemon
+ promote_active_rules
+ pwd
+ svn co https://svn.apache.org/repos/asf/spamassassin/trunk/rules 
https://svn.apache.org/repos/asf/spamassassin/trunk/rulesrc
/usr/local/spamassassin/automc/svn/trunk
Checked out revision 1887993.
Urulesrc/scores/72_scores.cf
Urulesrc/scores/scores-set0
Urulesrc/scores/scores-set1
Urulesrc/scores/scores-set2
Urulesrc/scores/scores-set3
Urulesrc/scores/stats-set0
Urulesrc/scores/stats-set1
Urulesrc/sandbox/jhardin/40_local_419replyto.cf
Urulesrc/sandbox/jhardin/40_local_googlestorage.cf
Urulesrc/sandbox/jhardin/20_misc_testing.cf
Checked out revision 1887993.
+ /usr/bin/perl build/mkupdates/listpromotable
HTTP get: https://ruleqa.spamassassin.org/last-net?xml=1
HTTP get: https://ruleqa.spamassassin.org/1-days-ago?xml=1
HTTP get: https://ruleqa.spamassassin.org/2-days-ago?xml=1
HTTP get: https://ruleqa.spamassassin.org/3-days-ago?xml=1
HTTP get: https://ruleqa.spamassassin.org/4-days-ago?xml=1
day 4 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 137.
HTTP get: https://ruleqa.spamassassin.org/5-days-ago?xml=1
HTTP get: https://ruleqa.spamassassin.org/6-days-ago?xml=1
+ mv rules/active.list.new rules/active.list
+ svn diff rules
+ cat /var/www/ruleqa.spamassassin.org/reports/LATEST
Index: rules/active.list
===
--- rules/active.list   (revision 1887993)
+++ rules/active.list   (working copy)
@@ -987,9 +987,6 @@
 MSOE_MID_WRONG_CASE
 
 # good enough
-NAME_EMAIL_DIFF
-
-# good enough
 NA_DOLLARS
 
 # tflags publish
@@ -1413,9 +1410,6 @@
 READY_TO_SHIP
 
 # good enough
-REPLYTO_EMPTY
-
-# good enough
 REPLYTO_WITHOUT_TO_CC
 
 # tflags publish
@@ -1635,9 +1629,6 @@
 TO_TOO_MANY_WFH_01
 
 # good enough
-TRANSFORM_LIFE
-
-# good enough
 TVD_IP_HEX
 
 # good enough
+ echo 'Committing promotions in rules/active.list...'
Committing promotions in rules/active.list...
+ svn commit -m 'promotions validated' rules/active.list
Sendingrules/active.list
Transmitting file data .done
Committing transaction...
Committed revision 1887994.
+ /usr/bin/perl masses/rule-qa/list-bad-rules
++ date +%w
+ [[ 3 = 3 ]]
+ echo 'From: aut...@sa-vm.apache.org (Rules Report Cron)'
+ echo 'Subject: [auto] bad sandbox rules report'
+ echo
+ cat /var/www/ruleqa.spamassassin.org/reports/badrules.txt
+ /usr/sbin/sendmail -oi d...@spamassassin.apache.org
+ for VER in $VERSIONS
+ make_tarball_for_version 3.4.4
+ version=3.4.4
+ tmpdir=/usr/local/spamassassin/automc/tmp/stage/3.4.4
+ rm -rf /usr/local/spamassassin/automc/tmp/stage/3.4.4
+ mkdir -p /usr/local/spamassassin/automc/tmp/stage/3.4.4
+ make clean
rm -f \
  SpamAssassin.bso SpamAssassin.def \
  SpamAssassin.exp SpamAssassin.x \
   blib/arch/auto/Mail/SpamAssassin/extralibs.all \
  blib/arch/auto/Mail/SpamAssassin/extralibs.ld Makefile.aperl \
  *.a *.o \
  *perl.core MYMETA.json \
  MYMETA.yml blibdirs.ts \
  core core.*perl.*.? \
  core.[0-9] core.[0-9][0-9] \
  core.[0-9][0-9][0-9] core.[0-9][0-9][0-9][0-9] \
  core.[0-9][0-9][0-9][0-9][0-9] libSpamAssassin.def \
  mon.out perl \
  perl perl.exe \
  perlmain.c pm_to_blib \
  pm_to_blib.ts so_locations \
  tmon.out 
rm -rf \
  *.cache blib \
  doc pod2htm* \
  qmail rules/*.pm \
  rules/70_inactive.cf sa-awl \
  sa-check_spamd sa-compile \
  sa-learn sa-update \
  spamassassin spamc/*.cache \
  spamc/*.o* spamc/*.so \
  spamc/Makefile spamc/config.h \
  spamc/config.log spamc/config.status \
  spamc/qmail-spamc spamc/replace/*.o* \
  spamc/spamc spamc/spamc.h \
  spamc/version.h spamd/*spamc* \
  spamd/spamd t/bayessql.cf \
  t/do_net t/log \
  t/sql_based_whitelist.cf version.env 
mv Makefile Makefile.old > /dev/null 2>&1
+ /usr/bin/perl Makefile.PL 
PREFIX=/usr/local/spamassassin/automc/tmp/stage/3.4.4
What email address or URL should be used in the suspected-spam report
text for users who want more information on your filter installation?
(In particular, ISPs should change this to a local Postmaster contact)
default text: [the administrator of that system] the administrator of that 
system

NOTE: settings for "make test" are now controlled using "t/config.dist". 
See that file if you wish to customize what tests are run, and how.

checking module dependencies and their versions...

***
NOTE: the optional MaxMind::DB::Reader module is not installed.

  Used by the RelayCountry plugin (not enabled by default) to
  determine the domain country codes of each relay in the path of an email. 
  Also used by the URILocalBL plugin (not enabled by default) to provide ISP
  and Country code based filtering.


***
NOTE: the optional MaxMind::DB::Reader::XS module is not installed.

  Recommended much faster version of the optional MaxMind::DB::Reader module,
  used by