Suresh Ramasubramanian <suresh@outblaze.com> wrote:

It is not just financial resources - it is also a factor of time to build a filter / set of filters from scratch (even with spamassasin + bogofilter you need to train it extensively, and tweak its rulesets to suit your mail flow).

there are some online spam archives that you can download and feed, and while it may take you a little time to write a script to push the archives at your spam filter (and if you push the archive at the filter multiple times, it may learn faster), you will have written a portable tool that you can use again and again, and will have tailored your email filters the way you want, rather than the way someone else wanted. teaching your users to foward spam to spam@yourdomain.com will also speed that process

Sometimes outsourcing corporate / isp mail handling to a provider like us, criticalpath, postini etc might be a good way to go.

i am no longer associated with them, but usa.net has some good stuff too, and while i would, for financial reasons, prefer to roll my own, outsourcing can be an effective way to manage your email, but it comes down to a cost/benefit analysis.

Or you might elect to get a managed antispam solution that plugs into your mta (kind of like brightmail or spamsquelcher.org)

brightmail is quite good

The unix way - one tool per job. Build a mail system out of components - it is often the best way to go.

i agree - like i said above, you can tailor it to suit your needs. one size does not necessarily fit all my $0.02 /joshua

srs

-- srs (postmaster|suresh)@outblaze.com // gpg : EDEDEFB9 manager, outblaze.com security and antispam operations

"Walk with me through the Universe, And along the way see how all of us are Connected. Feast the eyes of your Soul, On the Love that abounds. In all places at once, seemingly endless, Like your own existence." - Stephen Hawking -