Re: [Asrg] seeking comments on new RMX article

"Alan DeKok" <aland@freeradius.org> Mon, 05 May 2003 16:11 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06681 for <asrg-archive@odin.ietf.org>; Mon, 5 May 2003 12:11:09 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h45GJDf14042 for asrg-archive@odin.ietf.org; Mon, 5 May 2003 12:19:13 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45GJD814039 for <asrg-web-archive@optimus.ietf.org>; Mon, 5 May 2003 12:19:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06668; Mon, 5 May 2003 12:10:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Cia5-0006nH-00; Mon, 05 May 2003 12:12:45 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Cia4-0006nA-00; Mon, 05 May 2003 12:12:44 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45GFc813770; Mon, 5 May 2003 12:15:38 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45GAf813503 for <asrg@optimus.ietf.org>; Mon, 5 May 2003 12:10:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06377 for <asrg@ietf.org>; Mon, 5 May 2003 12:02:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CiRp-0006jJ-00 for asrg@ietf.org; Mon, 05 May 2003 12:04:13 -0400
Received: from giles.striker.ottawa.on.ca ([192.139.46.36] helo=mail.nitros9.org ident=root) by ietf-mx with esmtp (Exim 4.12) id 19CiRk-0006j3-00 for asrg@ietf.org; Mon, 05 May 2003 12:04:08 -0400
Received: from localhost ([127.0.0.1] helo=giles.striker.ottawa.on.ca ident=aland) by mail.nitros9.org with esmtp (Exim 3.34 #1) id 19CidB-0006dy-00 for asrg@ietf.org; Mon, 05 May 2003 12:15:57 -0400
From: Alan DeKok <aland@freeradius.org>
To: asrg@ietf.org
Subject: Re: [Asrg] seeking comments on new RMX article
In-Reply-To: Your message of "Mon, 05 May 2003 09:33:39 MDT." <200305051533.h45FXdNA004665@calcite.rhyolite.com>
Message-Id: <E19CidB-0006dy-00@mail.nitros9.org>
Sender: asrg-admin@ietf.org
Errors-To: asrg-admin@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/asrg/>
Date: Mon, 05 May 2003 12:15:47 -0400

Vernon Schryver <vjs@calcite.rhyolite.com> wrote:
> How does traceability and accountability reduce spam?  If you believe
> the DNS blacklist enthusiasts, most spam is already sufficiently
> traceable to be blocked.

  My experience has been different, as have others.

  Additional traceability means that it's more difficult for spammers
to send anonymously.  Once they're out in the open as spammers, then
blacklists become more useful.

  Note that blacklists only work against openly declared long-term
spammers.  "Stealth" spammers who use throw-away accounts, "hacked"
machines, etc. can easily circumvent any blacklist, unless the
blacklist reporting & distribution are both instantaneous.

  My experience with blacklists was that only about 10% of originating
IP's were on any blacklist, which made such lists useless to me.

> Why do you care more about tracing and accounting than not receiving
> spam?  That's a rhetorical question, but it involves what I think is
> an important point.

  I don't.

> However, unless you are spammer fighter interested in attacking
> spamemrs, you don't care who or where the spammers are if you can
> simply arrange to not receive their junk.

  I agree.  But I don't think such arrangements are trivial, or easily
made.

  Making more people accountable for their behaviour is just one more
tool in the fight against spam.  I've never claimed that any tool is
perfect, or that it will do everything.  In contrast, many people
violently oppose any system which *isn't* perfect, which makes me
wonder what the heck their agenda is.

> >   I'm at a loss to respond to such a position.  It's so trivially,
> > obviously wrong, that I'm left wondering what I'm missing.
> 
> You have grossly misrepresented what people have been saying.  No one
> has said that mail from from mobile users must be non-traceable and
> anonymous.  Thanks to SMTP-AUTH, STARTTLS, pop-before-SMTP, and other
> mechanisms, it is usually entirely traceable and not at all anonymous
> as far as the first MTA is concerned.

  Which misses entirely what I said.  A mobile user SHOULD use
SMTP-AUTH, STARTTLS, pop-before-SMTP, or other systems to
authenticate & secure his connection to his home domain.  So it's his
home domain which has done the hard work of verifying a previously
unknown, anonymous, roaming user.  Now that that's done, the
well-known, public, open MTA for the home domain can relay the message
to other well-known, public, open MTA's.

  The people going on about roaming users requiring naked SMTP to the
recipient domain haven't made it clear why it's the *recipients* job
to do authenticate them.  Isn't it easier for the home MTA to do
SMTP-AUTH, STARTTLS, etc., than it is for the recipient MTA to run the
message through crappy content filters?

  The MTA for the home domain has information which the recipient MTA
doesn't have, and may never have.  That information can be used to
reduce the work done by the recipient, to separate spam from
non-spam.  So the work of spam filtering is spread more evenly across
the network, and significantly less work is done, as a whole.  I fail
to see why there's any opposition to that goal.

  That's the entirety of my position in this matter.

  Alan DeKok.
_______________________________________________
Asrg mailing list
Asrg@ietf.org
https://www1.ietf.org/mailman/listinfo/asrg