Thanks for getting back - and looking up my profile is - special. :) 1) Agreed. So it's ~accurate~ really only for recipients that would use your service/the s

Thanks for getting back - and looking up my profile is - special. :) 1) Agreed. So it's ~accurate~ really only for recipients that would use your service/the same configuration/classification, right? For everyone else this is an approximation. With a nice api and some UI love, but still. 2) Agreed, a lot of things are unbeatable. But you yourself market this as 'most often the _content_ leads to classification as spam' solution. Everyone can change the content, good guy and bad guy. I'm not saying that the idea sucks and quite frankly someone involved into a business that sends unsolicited mail should know the deal already, but I still think that you're offering yet another testcase. Security by obscurity is not the problem, the thing is: Can I create a client for your API that randomly appends/prepends/inserts meaningful text into my crap content and evaluate your opinion on my crap x times per second? You commented elsewhere that you're not keeping my content, so - how are you going to notice this abuse? Okay, _NOW_ I'm too negative. Still - rate limit that stuff. :)