Hi nyet, You state this all as fact, but give no references to the source of the information, nor say why you'd know, e.g. an employee of Cloudmark. And what you say is incorrect because 'Razor servers' are not dead, some are still alive.
/etc/cron.d/amavisd-new has 18 */3 * * * amavis ... sa-sync 24 1 * * * amavis ... sa-clean The razor errors occur here every time sa-clean runs, 2019-03-15 01:24 +0000 2019-03-16 01:24 +0000 2019-03-17 01:24 +0000 2019-03-18 01:24 +0000 But only some of the times sa-sync runs 2019-02-22 09:18 +0000 2019-03-13 21:18 +0000 2019-03-14 09:18 +0000 2019-03-14 12:18 +0000 2019-03-14 18:18 +0000 2019-03-14 21:18 +0000 2019-03-15 00:18 +0000 2019-03-15 06:18 +0000 2019-03-15 09:18 +0000 2019-03-15 12:18 +0000 2019-03-16 00:18 +0000 2019-03-16 09:18 +0000 2019-03-16 15:18 +0000 2019-03-16 18:18 +0000 2019-03-17 03:18 +0000 2019-03-17 09:18 +0000 2019-03-17 12:18 +0000 2019-03-17 18:18 +0000 2019-03-17 21:18 +0000 2019-03-18 03:18 +0000 2019-03-17 06:18 +0000 worked fine, for example, and that's because of my explanation about DNS in comment #11. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819977 Title: razor2 had unknown error during get_server_info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1819977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs