I think rsync might be down if anyone can look.
On Sat, Mar 23, 2019, 00:43 root Fetching sa-update URLs from
> http://spamassassin.apache.org/updates/MIRRORED.BY
>
> http://sa-update.dnswl.org/ (116.203.4.105): UP (STALE since 1553307421)
>
> http://www.sa-update.pccc.com/ (69.171.29.42): UP (ST
Fetching sa-update URLs from http://spamassassin.apache.org/updates/MIRRORED.BY
http://sa-update.dnswl.org/ (116.203.4.105): UP (STALE since 1553307421)
http://www.sa-update.pccc.com/ (69.171.29.42): UP (STALE since 1553307421)
http://sa-update.secnap.net/ (204.89.241.6): UP (STALE since 1553307
On 22 Mar 2019, at 11:36, aut...@sa-vm1.apache.org wrote:
sa-vm1.apache.org : Mar 22 15:36:17 : automc : user NOT in sudoers ;
TTY=pts/0 ; PWD=/usr/local/spamassassin/automc ; USER=root ;
COMMAND=/bin/su -
Nothing to see here but me missing a step...
--
Bill Cole
b...@scconsult.com or billc.
sa-vm1.apache.org : Mar 22 15:36:17 : automc : user NOT in sudoers ; TTY=pts/0
; PWD=/usr/local/spamassassin/automc ; USER=root ; COMMAND=/bin/su -
On 22 Mar 2019, at 10:26, Tobi wrote:
> Hi
>
> Did not notice until now that my sa-update servers have been dropped.
> Seems on 31th December 2018. There was an issue with one server
> (37.252.124.130) on 30th december, had to install it new to fix it.
> According to my memory (tm) that was solved
Hi
Did not notice until now that my sa-update servers have been dropped.
Seems on 31th December 2018. There was an issue with one server
(37.252.124.130) on 30th december, had to install it new to fix it.
According to my memory (tm) that was solved beginning of January.
They should be back in play
+ promote_active_rules
+ pwd
+ /usr/bin/perl build/mkupdates/listpromotable
/usr/local/spamassassin/automc/svn/trunk
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
+ mv