Subscribe to
NSLog(); Header Image

SpamSieve 2.0

spamsieve-icon.pngSpamSieve 2.0 is out, and it's got a loooooooooong list of changes. I won't go over them here - you can click the link for yourself. What I will say is "free?" This update is free to registered users of 1.x. Were I Michael Tsai, I'd have had a hard time deciding whether or not to make this a $10 upgrade or to release it free. On one hand, $25 is an expensive add-on for something Mail does "for free" (though not nearly as powerfully). On the other hand, 2.0 adds so many features that I would have - and I suspect many others would have as well - gladly paid for an upgrade. Perhaps Michael will share his reasoning here or on his blog.

Of course, one thing this update does not do - and cannot do - is fix Entourage's inability to run rules on an email upon which an AppleScript has already acted. This means that I've got to pre-filter* all of my email, and only unfiltered email gets hit by SpamSieve. There's really no elegant way around this.

* Sales notifications from FSS sales go to a certain folder, some mailing lists get filed away, all comments from this blog are put in a certain folder and marked as read, etc.

2 Responses to "SpamSieve 2.0"

  1. It was a tough decision. First of all, it really is a major update. But I also think that updates should be free for at least six months. SpamSieve is a year old, and most people who bought it did so in the second half of that year. In the end, it didn't feel right to do a paid upgrade that penalized the early adopters who helped spread the word and make it a successful product. A bunch of them sent in $10 of their own volition, though, and I really appreciate that.

    I'd be interested to hear more about how your pre-filtering is set up. It seems like you should be able to get SpamSieve working with all your mail by adding the Run AppleScript action to the end of each terminal (i.e. message-moving or script-running) rule. Not elegant...but it works.

  2. Yeah, I may just tack it on to the end, at least to the filters that are so generic. One, for example, is "if account is xxxx then move to yyyyyy". I'll give that a try for awhile.