|
On 1/9/2012 4:15 PM, Colbeck, Andrew wrote:
<snip/>
SNFServer will reject a bad rulebase and keep running with the old one. So, if somehow a bad rulebase shows up then SNFServer won't crash... it will keep trying to get a new rulebase with the getRulebase script until it is successful. By default it will try about once every 3 minutes if it's not initially successful. However, once SNFServer is down for any reason, it will refuse to start without a good rulebase file to work with. The SNFClient utility can only attempt to ask SNFServer to scan a message -- it can't do it by itself. If SNFClient is not able to contact SNFServer and get a good answer then it will create SNFClient.exe.err to explain the problem and will return 0 to the calling program -- It returns 0 as a fail-safe so that the messages will go through. Better to allow all messages through than to block any good messages by mistake. On a well functioning system there should [almost] never be an SNFClient.exe.err file. I say [almost] because things happen from time to time on every system. However, if you see a .err message, check it out. If they persist - something is wrong. If you try to start SNFServer and it is unhappy, then download a fresh rulebase first. It's usually a good quick-fix. Best, _M -- Pete McNeil Chief Scientist ARM Research Labs, LLC www.armresearch.com 866-770-1044 x7010 ############################################################# This message is sent to you because you are subscribed to the mailing list <sniffer@sortmonster.com>. This list is for discussing Message Sniffer, Anti-spam, Anti-Malware, and related email topics. For More information see http://www.armresearch.com To unsubscribe, E-mail to: <sniffer-...@sortmonster.com> To switch to the DIGEST mode, E-mail to <sniffer-dig...@sortmonster.com> To switch to the INDEX mode, E-mail to <sniffer-in...@sortmonster.com> Send administrative queries to <sniffer-requ...@sortmonster.com> |
