[SATLUG] spam-fighting techniques

[Justizin]

On 10/27/06, Travis H. <solinym at gmail.com> wrote:
> Going over old email.
>
> > >> around.  Better to silently drop it into /dev/null than add to the
> > >> problem...
>
> Yep, it's called collateral spam.
>
> Me, I think it should be stored in the spam folder or appended to an
> archive, just in case.

Don't forget feeding vipul razor. :)

> I've been toying with the idea of creating a highly configurable but
> already very good mail distro or appliance.  I deal with tons of spam
> at Rackspace, and most of the time it is someone abusing a
> poorly-coded PHP form (header injection) or a user-level compromise
> (again, usually apache uid).  I think it needs to be configurable, or
> perhaps have a "randomized configuration", to keep spammers from
> compensating for a really successful product (pipe dream, perhaps, but
> look at what they're doing with bayesian filters).

FYI Tucows provides a managed service, but they've got to be your MX.
If you want to talk to their VP of Engineering I can put you in touch,
he's a very approachable fellow.  We have evaluated this for the ACM,
as Alain is the past president of ACM SIGGRAPH.

What do you think you would randomize?  An appliance is not a bad
idea, though I'm all for entirely managed services.  I use Google as
my MX and ZoneEdit for my DNS, though the latter stinks like rotten
eggs.

-- 
Justizin, Independent Interactivity Architect
ACM SIGGRAPH SysMgr, Reporter
http://www.siggraph.org/