This problem has caused me to stop using Spamassassin to do individual
reporting, and instead strip the emails and use razor itself to send spam
in batches. I've found this to decrease the errors substantially.
Additionally, now that I send in batches every 5 minutes, if razor refuses
the report,
Is there a way to determine if there is a problem with
the servers razor uses (such as an announce list or network status). Do
people find the razor (cloudmark) servers do not always accept spam
reports?
I've been getting
Nov 19 12:19:47.329814 report[2920]: [ 5] Connecting to
folly.cloudmark.c
Is anyone else seeing lots of timeouts for razor today? Seems to be timing
out a lot today. I tried changing the discovery servers, etc... but no
noticable difference.
Rob
---
This SF.net email is sponsored by: SF.net Giveback Program.
Sourc