Enabling SpamFoo
Question asked by echoDreamz - Today at 1:45 PM
Unanswered
@Tim - tbf, Sniffer and Cyren were garbage IMO. So being better than those 2 should not be hard :) We tested both over the years and neither were any good, blatant spam got thru, messages that were clearly not spam were flagged, both were not worth it.

Glad to see a new solution, we activated it last night on a test gateway and it did not seem to be doing anything, though, this could be because it's a free license?
Matt Petty Replied
Employee Post
Thanks for giving it a shot!

Try checking out the SpamFoo Dashboard from the system admin settings. This should give you a good scope into specifically what that client has done.

For logging, theres logs in this dashboard and there are logs (just like cyren/ms) in the Delivery log that should have some brief mentions of "[Spamfoo client]" you can try searching for that as well.

Please any one post how this works out, we'll be tracking this diligently throughout the weekend and into next week, ready to make any changes (as seen) we need.

P.S. Also don't forget to try enabling the classifications on one (or all) of your domains via the features to see the other half of SpamFoo, which has certainly done a good job of cleaning up my inbox with a lot of "junk" going into transactions/updates and keeping an extra close eye on my Primary.
Matt Petty
Senior Software Developer
SmarterTools Inc.
David Fisher Replied
I am thinking SpamFoo WILL NOT work on a gateway, it has to run on the same server your domains and users are on. From everything I read it points to this.

I sure hope this is not true, because, like others, I believe you should have a couple gateway servers it from of SmarterMail's mail Mail Server for various reasons.  Most large providers do this, Microsoft and GMail do not have their main customer server the incoming email server.

  That is why also there needs to be a way for Port 25 to be SMTP Auth Only!
echoDreamz Replied
David, yeah, after reading how it works, it makes more sense that it is on the actual end-user SM host. As for SMTP auth, yes... wish we could tell SM which (in our case all) SMTP ports are auth only (unless IP is whitelisted).

Reply to Thread

Enter the verification text