C-Command Software Forum



This is driving me nuts. I have looked and relooked at the installation instructions and am confident it is correct. Using 2.7.2. Then, I looked at the attached log, but it puts me to sleep!

One thing I noticed was a spam marked good due to whitelist. There are quite a few of these; I have an older whitelist I could substitute but have not messed with it or the corpuses per your instructions. Thanks.

It looks like all of the problems occurred when using SpamSieve 2.6.5. That version is more than a year old. The current version is 2.7.2.

Your history database is damaged, which makes it hard to see what’s happening in the log. After updating to 2.7.2, please hold down the Command and Option keys when launching SpamSieve and then click Reset History.

It also looks like you need to reset the corpus and re-train SpamSieve.

Michael, thanks.

I wonder if using a known good corpus would be useful?

I tried importing but it is not clear where the corpus is located.


It’s best to train SpamSieve with your own recent messages, both spam and good.

Old corpus was 30 megs. Ouch.

Best to retrain, yes, slowest also. Replaced the SS folder with a known good one and all is well. This whole thing came from using a backup laptop while the iMac was in the hospital.