Company News Products Tools Support Documentation Q & A Contact Us

Q & A Home
Customizing SNF
Errors
False Positives
Functionality
Integration
Log Files
Resellers
Result Codes
Rulebase Updates
Software
Spam
Subscriptions
Trials
Version 3 Architecture
Documentation Home

Rulebase Updates

I have been having trouble with my update script. Nothing has changed, so what could be wrong?

Here is an account from one of our users to solve this problem:

I just wanted to let you know these past few days I have had to manually update Message Sniffer by running the .cmd file. I reviewed the logs this morning and noticed emails were still being received from updates@armresearch.com, the receiving account configuration had not changed (Configured to run .cmd file when email received from updates@armresearch.com). So, I reviewed all of the account settings and noticed the default quota settings of 200 messages / 50mb for this account.

To resolve this I added the following line before the ENDLOCAL:

REM ===== ERASE UPDATE MESSAGES ==========================================
ERASE "C:\MDaemon\Users\sellersinsurance.com\snf.updates\*.msg" /Q

This way the account doesn't store the messages, will not exceed quota, and I still have the logs to refer back to for troubleshooting.