I tested several times with: echo "test" | spamassassin -D razor2 2>&1 | less
Sometimes the error occurred, other times not. The only difference was that - when it worked - it showed:
Mar 15 11:12:48.739649 check[21141]: [ 8] Discovery Server discovery.razor.cloudmark.com replying with nsl=n002.cloudmark.com
whereas on the other hand, when it didn't work, it showed:
Mar 15 11:13:06.607983 check[21146]: [ 5] Razor Discovery Server discovery.razor.cloudmark.com had no valid nsl servers
So for me it seems that the remote site has some trouble, not the client installations.
Hope, they fix it soon.
Seems to be a server error from the remote site.
I tested several times with: echo "test" | spamassassin -D razor2 2>&1 | less
Sometimes the error occurred, other times not. The only difference was that - when it worked - it showed: razor.cloudmark .com replying with nsl=n002. cloudmark. com
Mar 15 11:12:48.739649 check[21141]: [ 8] Discovery Server discovery.
whereas on the other hand, when it didn't work, it showed: razor.cloudmark .com had no valid nsl servers
Mar 15 11:13:06.607983 check[21146]: [ 5] Razor Discovery Server discovery.
So for me it seems that the remote site has some trouble, not the client installations.
Hope, they fix it soon.