A damaged statistics database can cause SpamSieve to crash, report internal errors, or show incorrect accuracy numbers in the Statistics window. Database damage can be caused by crashes or disk errors.
If you have a backup from before the damage occurred, you can quit SpamSieve and your mail program and replace the file:
/Users/<username>/Library/Application Support/SpamSieve/History.db
with a working copy. See the How can I open the Library folder? section for how to find this file.
Otherwise, you can have SpamSieve reset the database and start a new one. (This will not affect SpamSieve’s training data or filtering accuracy.)
Quit SpamSieve and your mail program.
Open your Applications folder and select SpamSieve.
While holding down the Command and Option keys on the keyboard, double-click the SpamSieve icon.
Note: If holding down the Command and Option keys does not work for you, you can instead enter this command:
defaults write com.c-command.SpamSieve ShowResetAlert YES
into Terminal and press Return before launching SpamSieve.
Click the Reset History button in the window that pops up.