Matt Kettler-3 wrote: > > > .. > Yes, we know that. Our tool is external too. > > The only big difference I see is your tool appears to be a quasi > nonstandard milter for sendmail, that interacts with all phases of > delivery. > > Personally, I use a combination of milter-greylist for filtering before > the DATA phase, and MailScanner/SpamAssassin for post delivery scanning. > Works really nicely and does about 95% of what you mention. It won't > look up text domain names in RBLs or URIBLs though, only IP based RBLs > are currently supported. > ... >
Well, don't know about non-standard :-), but this blocker definitely interacts with all phases of delivery :-) I'm not necessarily suggesting anyone abandon SpamAssassin - don't get me wrong about that - I just wanted to come up with something that blocked spam at the protocol level (so the spammer gets an error!!!), and was highly efficient and simple to get working on a system. I'm not sure what we're going to do with our "product" beyond our own systems, and for use on some of the big sites my group manages. I am the MIS director for a couple of municipalities, along with some other sites, and spam was becoming a real issue. We evaluated a number of available products, both commercial and not, including Ironmail, Barracuda networks, SpamAssassin and some others I can't think of right now. For us, because we have a couple of software engineers on staff, writing a blocker turned out to be practical, and in this case, the best alternative. Currently, a configuration user interface (graphical, web based) is in the works, to allow individual users to have whitelists, blacklists, etc. and determine the filtering level for their own particular needs, if the default system-wide settings are not to their liking. You know, feature creep :-) "oh, but we could add this one thing".... Regards, Steve -- View this message in context: http://www.nabble.com/Yet-another-spam-blocker--tp15911630p15920983.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
