On 06/08/2017 05:46 AM, Reindl Harald wrote:
it worked exactly one time
Am 06.06.2017 um 17:29 schrieb David Jones:
FYI We have the rule build scripts working for updates via sa-update.
Default rule scores are also updating thanks to our masscheckers out
there.
https://wiki.apache.org/spamassassin/NightlyMassCheck
[root@mail-gw:~]$ cat sa-update.log
01-Jun-2017 01:49:07: SpamAssassin: No update available
02-Jun-2017 01:15:09: SpamAssassin: No update available
03-Jun-2017 01:46:22: SpamAssassin: No update available
04-Jun-2017 00:37:18: SpamAssassin: No update available
05-Jun-2017 00:03:52: SpamAssassin: No update available
06-Jun-2017 00:02:18: SpamAssassin: No update available
06-Jun-2017 19:28:42: SpamAssassin: Update processed successfully
07-Jun-2017 00:44:05: SpamAssassin: No update available
08-Jun-2017 01:29:45: SpamAssassin: No update available
Is it possible that you have something else running sa-update and not
logging to that sa-update.log? The time on 06-Jun seems to indicate
that a special manual run was done out of the normal time period of the
other log entries.
Run this and see what your 'channel cf' file is:
sa-update -D -v
The first line in that cf file is the SVN version number that was
installed by sa-update.
head -1 /var/lib/spamassassin/3.004001/updates_spamassassin_org.cf
# UPDATE version 1797895
The current version should be 1797895 for about 14 more hours.
--
Dave
