Re: several messages

"Chris Lewis" <clewis@nortel.com> Thu, 13 November 2008 17:43 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2D80E28C1E6; Thu, 13 Nov 2008 09:43:56 -0800 (PST)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6495E28C1E6 for <ietf@core3.amsl.com>; Thu, 13 Nov 2008 09:43:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.63
X-Spam-Level:
X-Spam-Status: No, score=-5.63 tagged_above=-999 required=5 tests=[AWL=-0.323, BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DB3YgmZr3W3F for <ietf@core3.amsl.com>; Thu, 13 Nov 2008 09:43:53 -0800 (PST)
Received: from zcars04f.nortel.com (zcars04f.nortel.com [47.129.242.57]) by core3.amsl.com (Postfix) with ESMTP id 4E8DD28C1FA for <ietf@ietf.org>; Thu, 13 Nov 2008 09:43:53 -0800 (PST)
Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id mADHhob15113 for <ietf@ietf.org>; Thu, 13 Nov 2008 17:43:50 GMT
Received: from zrtphx5h0.corp.nortel.com ([47.140.202.65]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 13 Nov 2008 12:43:35 -0500
Received: from [47.129.150.171] (47.129.150.171) by zrtphx5h0.corp.nortel.com (47.140.202.65) with Microsoft SMTP Server (TLS) id 8.1.311.2; Thu, 13 Nov 2008 12:43:34 -0500
Message-ID: <491C673F.4030402@nortel.com>
Date: Thu, 13 Nov 2008 12:43:27 -0500
From: Chris Lewis <clewis@nortel.com>
Organization: Nortel
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: several messages
References: <Pine.LNX.4.44.0811121356250.4831-100000@citation2.av8.net> <200811121948.OAA16913@Sparkle.Rodents-Montreal.ORG>
In-Reply-To: <200811121948.OAA16913@Sparkle.Rodents-Montreal.ORG>
X-OriginalArrivalTime: 13 Nov 2008 17:43:35.0516 (UTC) FILETIME=[5A6C79C0:01C945B7]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

der Mouse wrote:
>>> It _does_ mean that someone to whom email is important had better do
>>> due diligence in selecting DNSBLs - just as someone to whom a car is
>>> important had better do due diligence in selecting a mechanic [...]
>> I agree with that.  But easier still is to setup your own spam traps
>> and run your own spamfilter.  Which is what I think most actually do.

> Not easier for me; not easier for the ISP I work for (I'm part of its
> collective postmaster).  I, at home, and we, at work, find DNSBLs by
> far the lower-cost answer, after all the costs are tallied (dollars
> spent, human time, false positives, false negatives, machines, disk
> space, network bandwidth, the list of forms costs can take is long).

In today's climate, you have to have very large spamtraps to do an
effective job in driving your own filters unless you have an atypical
spam load.  If you have users that are being hit by BOTnets, your
spamtrap has to be in the 100s of thousands of emails per day, if not
larger, to be able to derive the right information to tune filters to an
effective level.

We're a large company, and we've been able to, through our legacy
domains and "gracious donations" to get our traps up to about 10-20M per
day.  That alone does a pretty good job.  But even we, despite how big
our traps are and how well they do, get considerable extra effectiveness
by using DNSBLs.  At least one of these DNSBLS, via mutterings in the
woodworks, has spamtraps that are effectively more than 2 orders of
magnitude bigger than ours.  Yikes.

Someone of the size of AOL or Gmail can do the spamtrap game all by
themselves - internally, they usually generate source IP reputation
lists (however distributed) in addition to other techniques to use that
information.  But almost everyone smaller needs much more trap than they
can realistically construct themselves.

Small sites with usually atypical spam loads can often do just fine with
very much smaller data sources.  It's amazing how much different the
spam profile can be at small sites.  But they generally don't work
nearly as well once scaled up to larger environments with more
representative loadings.

As one datapoint to show how uneven spam distribution is: we have 45,000
recipients.  Fully half of them get virtually no spam at all.  If we
segregated those people off on their own mail servers, they wouldn't
need filtering.  Meanwhile, the other half get lots.  One poor sod was
getting 4,000-16,000 spams/day for the better part of a year - no
useable commonality whatsoever in what he was getting nor where it was
coming from.  The only explanation for that, ironic as it may be, is
that he was on lots of IETF mailing lists for a very long time that got
scraped over and over again.  The only solution - just what got past the
filters at 99%+ effectiveness was overwhelming - was for him to change
his email address (actually we all did, the company domain name got
changed.  Not because of this, but it helped anyway, causing a huge
discontinuity in spam volumes.).

[Most of the high rollers in our "spam sweepstakes" are long-term IETF
mailing list members on the same address... Long-term IEEE list
membership is also a big factor.]
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf