On 07/06/2017 12:02 PM, Rainer Sokoll wrote:
Am 06.07.2017 um 18:55 schrieb David Jones <djo...@ena.com>:
You can also run 'sa-update -vvv' to see more information on what it's looking
for.
Now I'm really confused: it works the way described in this thread:
root@mx1:~# sa-update -vvv
DNS TXT query: 0.4.3.updates.spamassassin.org -> 1799552
Update available for channel updates.spamassassin.org: 1786640 -> 1799552
DNS TXT query: mirrors.updates.spamassassin.org ->
http://spamassassin.apache.org/updates/MIRRORED.BY
fetching http://spamassassin.apache.org/updates/MIRRORED.BY
http: (curl) GET http://spamassassin.apache.org/updates/MIRRORED.BY, success
fetching http://sa-update.secnap.net/1799552.tar.gz
http: (curl) GET http://sa-update.secnap.net/1799552.tar.gz, success
fetching http://sa-update.secnap.net/1799552.tar.gz.sha1
http: (curl) GET http://sa-update.secnap.net/1799552.tar.gz.sha1, success
fetching http://sa-update.secnap.net/1799552.tar.gz.asc
http: (curl) GET http://sa-update.secnap.net/1799552.tar.gz.asc, success
Update was available, and was downloaded and installed successfully
root@mx1:~#
That's odd. Nothing has changed in DNS for almost 2 weeks so that
shouldn't have happened. Can you post the contents of
/etc/cron.daily/spamassassin so we can see what it's trying to run?
--
Dave
