Folks,
With respect to the OSIRU DNS problems recently, we had the situation where SpamAssassin suddenly went from taking one second to process a message to 30 seconds or more. Mail suddenly started backing up, and we ended up with a real train wreck - mail volume was much higher than usual due to the Sobig virus.
Would it be possible to have SpamAssassin log some sort of error message, at least when run in debugging mode, indicating what specifically has timed out or returned some sort of strange DNS error? I browsed through the code, but didn't see any obvious way to do that. It would be helpful to note if Razor, DCC, or others timed out in the same painful way.
Although I don't have the answer to your question, I suggest you look at using the following options to reduce the various timeouts to minimize the chance of a "train wreck" due to things outside your control :)
rbl_timeout razor_timeout dcc_timeout pyzor_timeout
I set them all to 10 seconds to minimize backing up if there are any outages... you may want to go as low as 5, but if you go much lower than that you'll probably find tests failing when they shouldn't...
Regards, Simon
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
