Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: [Original edit by Dave]

...

Hostname

Function

Software

Configs/Location

Resource/URL

SVN Location

incoming.apache.org

Donated by Sonic

 

 

 

 

sa-vm1.apache.org

DNS Hidden Master

PowerDNS

/etc/powerdns/pdns.d/pdns.local.conf

spamassassin.org

dns (webserver API key redacted)

 

Rsync Mirrors

rsyncd

/etc/rsyncd.conf

rsync.spamassassin.org

trunk/build/automc/etc-rsyncd.conf

 

Web Server

apache2

/etc/apache2/sites-available/automc.conf

updates.spamassassin.org

trunk/build/automc/automc-apache2.conf

 

 

apache2

/etc/apache2/sites-available/automc.conf

ruleqa.spamassassin.org

trunk/build/automc/ruleqa.cgi

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="9761ad4befb0e6c1-77a8de14-4bc84fe2-9eecb85c-5408fd6fbad636b467cbf7db"><ac:plain-text-body><![CDATA[

 

sa-update mirrors

svn

rsyncd [updates] for mirrors

spamassassin.apache.org/updates

[site/updates

http://svn.apache.org/repos/asf/spamassassin/site/updates/]/MIRRORED.BY

]]></ac:plain-text-body></ac:structured-macro>

 

Nightly Masscheck

cron/scripts

/usr/local/spamassassin/automc/html

ruleqa.spamassassin.org

trunk/backend/nitemc/README

...

There are currently (June 2017) two different rule daily updates. Both do lint tests against the latest version of SpamAssassin but the first one updates the 72_scores.cf based on the masscheck contributions.

Wiki Markup
 *25 2 \* \* \* automc *~/svn/trunk/build/mkupdates/do-stable-update-with-scores

*
  **~/svn/masses/rule-update-score-gen/do-nightly-rescore-example.sh

*
   **~/svn/masses/rule-update-score-gen/generate-new-scores.sh

*
    *uses ~/tmp/generate-new-scores for SVN work
area
*sorts out the usable corpus from the latest 'SVN revision' at the top of the submitter's log file which should match the latest tagged build of SVN rules
*checks the sorted corpus for a minimum number of valid contributors and ham/spam
 area
    *sorts out the usable corpus from the latest 'SVN revision' at the top of the submitter's log file which should match the latest tagged build of SVN rules
    *checks the sorted corpus for a minimum number of valid contributors and ham/spam
  **~/svn/trunk/build/mkupdates/mkupdate-with-scores

*
   *uses ~/tmp/sa-mkupdate for SVN working area


   *gets latest SVN $\{REVISION\} from rulesrc/scores/score-set\*


   *masses \-> perl Makefile.PL && make (complete build of SA and test)


    *perl hit-frequencies


    *garescorer - compiles and runs it, requires build/pga


  *sends email if not enough masscheck submitters or usuable ham/spam for the latest SVN revision


  *updates DNS
entries for 2
 entries \[0-3\].3.3.updates.spamassassin.org
and
 - newer 3.
3.3.updates.spamassassin.org (currently all supported versions of SA use this DNS entry via CNAMEs)
30 8 * * * automc
4.x versions have a CNAME to 3.3.3.updates.spamassassin.org
 *30 8 \* \* \* automc *~/svn/trunk/build/mkupdates/run_nightly* > /var/www/automc.spamassassin.org/mkupdates/mkupdates.txt


  *creates new rules/active.list


  *commits new rules/active.list


  *runs spamassassin lint against the updated rules and checks in a tagged version of 'sa-update_$\{SA_VERSION\}_$\{TSTAMP\}'


  *creates REVISION.tgz REVISION.tgz.sha1 and REVISION.tgz.asc in /var/www/automc.spamassassin.org/updates that is rsyncd to mirrors for sa-update


  *updates DNS
entries for 2
 entries \[0-3\].3.3.updates.spamassassin.org
and
 - newer 3.4.x versions have a CNAME to 3.3.3.updates.spamassassin.org
(currently all supported versions of SA use this DNS entry via CNAMEs)

nitemc (prepares client masscheck area from latest tagged build of SVN rules)

...