SpamSieve has been updated to version 2.7.3. This is a free update that includes the following changes:
Rewrote and restructured the manual to make the setup andtroubleshooting instructions clearer.
Replaced the Training Tip
window with an alert that’sdisplayed when SpamSieve’s corpus is empty. This goes along withthe more explicit guidance that ongoing training is onlynecessary to correct mistakes. - The Entourage installer no longer asks before replacing existingscript files. If you want to customize the scripts (rare these days,since there are so many built-in configuration options), you should usecopies with different names to avoid having SpamSieve overwrite them.
Changed the recommended Entourage rule setup to better handleuncertain messages. The installer now creates the Uncertain Junk
category if necessary. - Made the Apple Mail plug-in installer more robust.
Worked around a problem parsing certain multipart messages.
Adjusted the built-in blocklist rules for better accuracy.
Reduced memory usage when processing message attachments.
Fixed a bug sorting in rules windows.
Fixed a bug marking incoming Entourage messages as Uncertain Junk.
Error on install
When I try to download 2.7.3 I get a message “Cannot open file”.
Mac 10.5.6, Apple Mail. I’ve restated computer and get the same message
Which application is showing the error? Which application did you use to download the file? What is the last thing you did before seeing the error message?
steps to getting error message
I have the SS automatic check for updates on, and go the Software Update notice that you posted at the beginning of this thread.
I’ve tried clicking both the Download and Download & Install buttons, but get the error message with both. The downloading progress bar shows for a second, and then the message appears. I’ve looked in my Downloads folder but don’t find anything with SpamSieve name.
Thanks. It looks like the problem was not in opening the file but in downloading it from the SpamSieve server. You were able to download the file later, so perhaps it was just a transient network or server problem.