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): UP (CURRENT)
http://sa-update.secnap.net/ (204.89.241.6): DOWN
http://sa-update.space-pro.be/ (176.28.55.20):
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): UP (CURRENT)
http://sa-update.secnap.net/ (204.89.241.6): DOWN
http://sa-update.space-pro.be/ (176.28.55.20):
spamassassin.org:
pdnsutil list-zone spamassassin.org
OK (use 'load-zone spamassassin.org FILE' to restore)
svn status /usr/local/spamassassin/automc/svn/dns
M /usr/local/spamassassin/automc/svn/dns/spamassassin.org
OK
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): UP (CURRENT)
http://sa-update.secnap.net/ (204.89.241.6): DOWN
http://sa-update.space-pro.be/ (176.28.55.20):
On 19 Sep 2020, at 14:25, Kevin A. McGrail wrote:
I've seen it be wonky too, it's not just you.
Indeed, it is evidenced by the 23:18 UTC mail from
checkSAupdateMirrors.sh, which does not include the Secnap mirror. The
messages before and after it do. You can also correlate the commits that
I've seen it be wonky too, it's not just you.
On 9/19/2020 12:39 PM, Bill Cole wrote:
> On 19 Sep 2020, at 12:34, Bill Cole wrote:
>
>> Both Kevin & I made changes to MIRRORED.BY with the goal of retiring
>> the Secnap mirror, and repeatedly it got reverted in the copy used by
>> the monitoring
On 19 Sep 2020, at 12:34, Bill Cole wrote:
Both Kevin & I made changes to MIRRORED.BY with the goal of retiring
the Secnap mirror, and repeatedly it got reverted in the copy used by
the monitoring script.
Don't believe it? Compare these:
Both Kevin & I made changes to MIRRORED.BY with the goal of retiring the
Secnap mirror, and repeatedly it got reverted in the copy used by the
monitoring script.
Don't believe it? Compare these:
https://svn.apache.org/repos/asf/spamassassin/site/updates/MIRRORED.BY
+ promote_active_rules
+ pwd
+ svn co https://svn.apache.org/repos/asf/spamassassin/trunk/rulesrc
/usr/local/spamassassin/automc/svn/trunk
Urulesrc/scores/72_scores.cf
Urulesrc/scores/scores-set0
Urulesrc/scores/scores-set1
Urulesrc/scores/scores-set2
U