Ugh. I don’t think you are understanding what I’m saying (and I think others), so I will try one last time and won’t respond again.
What you are suggesting (“This would include SpamSieve’s built-in blocklist rules (which you could uncheck to disable if you don’t want them)”) is work on my part. I have to read and understand your built-in blocklist rules to see if I would want to uncheck them. I do not want to work and figure this out. I just want your product to be able to do two things: 1) Do what you already do to move suspected messages to a spam folder for review. Do it as you already do. 2) Allow me to manually specify a block list of known senders which should not be allowed and block those (auto-delete). The block list should work the way it does for phone calls and iMessages in iOS. They are blocked, i.e., they are not received at all. Not quarantined. Nothing. Not received.
A block list should operate differently than a list of suspected bad messages. The two should not be mixed. But it appears that they way things are currently implemented in the product, it does not appear to me that SpamSieve cannot absolutely distinguish between an email address I want blocked and a message I have indicated as “Train as Spam.” How do you know I didn’t mark one message “Train as Spam” based on the content (not the sender) and another based specifically on the sender?
It quickly gets tricky to auto-delete based on content or subject. I might receive a forwarded message that is spam but the forwarder asked me some question about it. I want to see that. That sender may not be in my contact list so cannot automatically be whitelisted.
I just want to be able to blacklist a specific email address and never see anything from it again…again, just as phone and iMessage blocking works. All the rest should go to the spam folder for review.