Made some changes to better support the upcoming Microsoft Outlook 2011. (Full support will come when Office ships.)
Added various updates and clarifications to the manual.
Fixed a regression where SpamSieve wouldn’t be able to install its Apple Mail plug-in if Mail’s folder had been redirected using an alias.
Fixed a bug where SpamSieve would sometimes quit when coming out of trial mode.
Fixed a bug where sometimes the Hits
column in a rules window couldn’t be resized. - Worked around an OS bug that could cause an internal error when reporting a corpus error.
Made various modernizations to SpamSieve’s code and interface files.
The Apple Mail plug-in now shows up with the proper name in Mail Plugin Manager.
I just went through the checklist and everything is good. I’ve been using SpamSieve for years successfully (and like it).
I did the test and it worked as expected, using one of the spam emails I got after installing 2.8.3 (that I had already trained as spam) as the test case.
According to your log file, you’ve trained SpamSieve with three spam messages since updating to 2.8.3. One of them was a lottery message that SpamSieve gave a score of 18. The other two were similar messages from the same address where the first one got a score of 27. So it thought both of these messages were borderline, and I don’t see this as a major change. Just unlucky, perhaps.
Kind of amazing that 3 qualifies as a noticeable amount of spam with SpamSieve
Okay, if it looks good to you, that’s all I wanted to hear. If it stays at that level, I’ll let you know (I generally get 3 spam a month – at least that’s what it feels like).
I also noticed that I was getting more spam after this update. I followed the setup verification listed above, and found that my rules did not have SpamSieve checked as active. I never use those mail rules myself, and the last time I even went in there was when I first installed SpamSieve years ago. Did something happen with this update that turned the switch off during the install?
There is a bug in the non-English localizations that makes the blocklist and whitelist windows not open. However, this does not affect the filtering accuracy. Please contact spamsieve@c-command.com for a workaround.
Amen!
Long time fan, short term unhappy. There is simple NO question the new update allows SIGNIFICANTLY more spam to get through…much of which appears “obvious.”
This is not a user “setting” issue, this is a programmer issue. FIX IT or on to better solutions.
Based on the symptoms you describe and the lack of other reports of problems like this, I think it’s likely that there’s a setup or training problem on your particular Mac. However, either way, if you’d like a solution please send in a report so that I can investigate where the problem is.
