Then again, maybe I won’t need to make any rules, and it’s a moot point. The blocklist has a “hits” column, so in a couple of weeks/months, I can see which rules haven’t matched anything and remove them. If you go that route, you’ll need to maintain them or you’ll have a mess on your hands. The rules in the blocklist feel too specific. The configuration isn’t difficult, but you need to be 100% accurate and double check your work or nothing gets filtered. It’s not an expensive app, nor is it a subscription, so that’s points in its favor. With SpamSieve now working, and trashing messages, in a good way, is it worth it? We’ll check on that after letting it run a while. Adding the message details to the corpus is a good idea, but a rule for every single email sender isn’t maintainable in the long run. Or at least perform the training and edit the rule to be more general and work on more than a single message. Moving forward, if rules are needed, I will add them to the block instead of training them as spam. It also looks like the same incorrect usage I had. That looks like a performance and maintenance nightmare. While that seems like a total exaggeration, and nothing I’ve experienced yet, I’ve seen screenshots with 20k blocklist rules. Messages will take 10 minutes to get delivered and the entire system will come to a crawl. If you keep that up, SpamSieve will be so choked with rules it will suffocate under its own weight.Ī message will filter through 20k rules only for it to not match any criteria. They are too specific and will work once, then never again. I still think that’s an issue with the way SpamSieve builds rules when you Train as Spam. Checking for a sender of or is pointless. None of those rules were worth keeping as they were too specific. And to be honest, those are kind of spammy, even though not actual spam.Īfter realizing my mistake, I deleted the Blocklist and started over. It’s now up and running correctly, tossing away 40+ messages a day with only two or three being false positives. Simply put, I missed a step, which prevented the filtering of messages. To be fair, the initial problem with SpamSieve not detecting spam messages was a configuration issue on my part.

Spamsieve accidentally markes as spam