When users select "Mark as Spam" in a message the only thing it affects is their own personal Mailbox and Bayesian Filtering for the Server (if enabled). SmarterMail does not have a reporting mechanism to RBLs (many RBLs don't have a reporting mechanism to report to as they gather IPs based on Spam Trap activity to reduce "false positives"), or to Feedback Loops (as there are many different formats, ARF, JMR, and proprietary ones used by Google, and SendGrid, and ReturnPath requires a subscription to their service to participate in submitting to their FBL).

So i have Updated this thread from a question to a suggestion.

"Make it do something"

 

Dear Smarter Peeps of Smarter Tools :With all of the thousands of smarter Mail installations out there, I think you have a golden opportunity to start up your own blacklist service or some type of shared community resource.  Every time someone clicks :"mark as spam" it could report that spam email back to you and you guys could build a database of these emails.  then set up smarter mail to compare its own built in spam filtering to that database.  How many total mailbox users do you guys have ? If only 10% participated, it could be instant success for smarter mail, an possibly a faster response time (time to detection) to other services.

 

How many times i have marked something as spam, then it shows up again a few days or even hours later, but from what appears a different email address. using content comparison, this could stop almost immediately.  We used to use a product a few years ago called Mail Washer Pro, it used content comparison, not just IP blacklisting.

They have a server version :

 

Any updates on this ?

Hey, Curtis

 

First of all, starting our own blacklist is an interesting idea. We'll have to toss that around the office here. We'll also take a look at Mailwasher and see if there's any integration possibilities. No guarantees, but we'll certainly look into it.

 

As for "mark as spam" doing something, it does. Realize that Mark as Spam is a Bayesian tool. That means that there is a learning process needed before any "automatic" action is taken on a message. As there is that learning period, it's not uncommon that a similar message to one recently marked would come into your inbox. You have the ability to manage how many messages are necessary for the filter to update by editing the Bayesian Filtering spam check. I think it defaults to a pretty high number, but lowering that to 200 or so wouldn't hurt...but you can set that to whatever you want. 

 

That said, we're also exploring the potential to tie Mark as Spam back to Cyren and/or MessageSniffer so that we DO actually report messages to a "RBL". 

Hi

I have to look for my notes. I had more ideas about this recently and was actually going to start designing some type of plugin or API or something and show you. I have about a page of notes on how this could be done, and i think it could be really big. I would be interested in even partnering with you guys on this. Let me hunt down my notes and get back to you. I think you will love what I had mapped out as a process.