Re: [Asrg] Spam, why is it still a problem?

Barry Shein <bzs@world.std.com> Mon, 16 January 2006 18:00 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EyYec-00072L-EW; Mon, 16 Jan 2006 13:00:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EyYeb-00071w-5d for asrg@megatron.ietf.org; Mon, 16 Jan 2006 13:00:29 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02407 for <asrg@ietf.org>; Mon, 16 Jan 2006 12:59:04 -0500 (EST)
Received: from pcls3.std.com ([192.74.137.143] helo=TheWorld.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EyYmY-0003i2-73 for asrg@ietf.org; Mon, 16 Jan 2006 13:08:43 -0500
Received: from world.std.com (root@world.std.com [192.74.137.5]) by TheWorld.com (8.12.8p1/8.12.8) with ESMTP id k0GI0B2A006424 for <asrg@ietf.org>; Mon, 16 Jan 2006 13:00:11 -0500
Received: (from bzs@localhost) by world.std.com (8.12.8p1/8.12.8) id k0GHxTNC021579; Mon, 16 Jan 2006 12:59:29 -0500 (EST)
From: Barry Shein <bzs@world.std.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <17355.57089.337059.779704@world.std.com>
Date: Mon, 16 Jan 2006 12:59:29 -0500
To: asrg@ietf.org
Subject: Re: [Asrg] Spam, why is it still a problem?
In-Reply-To: <OF4768D65E.ECA3CB39-ON802570F8.004A9BA8-802570F8.004AA408@slc.co.uk>
References: <OF4768D65E.ECA3CB39-ON802570F8.004A9BA8-802570F8.004AA408@slc.co.uk>
X-Mailer: VM 7.07 under Emacs 21.2.2
X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.1.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pcls3.std.com
X-Virus-Scanned: ClamAV 0.86rc1/1243/Sun Jan 15 13:35:18 2006 on pcls3.std.com
X-Virus-Status: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7bit
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
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>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org

 > We could probably knock together a modern interoperability
 > specification which would accomodate these, and many other, factors but
 > what use would it be? We would then have to convince every user of mail to
 > upgrade their software, and if we manage that what cost would it have?
          ...
 > If you want spam to stop dead you only need to replace SMTP as the mail
 > transport protocol of choice for everyone everywhere at once.


I would like to introduce a new term to spam-fighting, analogous to
FUSSP ("final ultimate solution to the spam problem" or something
close to that):

                                IFUSSP

      The IMAGINARY Final Ultimate Solution to the Spam Problem.

>From the first nanosecond spam was recognized as something which
needed some sort of generalized solution people involved have repeated
to each other over and over:

      The problem is you can't just replace all the mail software
      overnight on either clients or servers which makes a practical
      solution very difficult.

           (I'll call that the First Axiom of IFUSSP)

Sounds good, but I claim there is no such solution, or it's never been
outlined that I've seen.

Someone please outline it and let others work on deploying its
acceptance. The latter, deployment, is a management function about
which a brilliant software designer may have little insight. Why
proclaim onself expert in both the design and its practical
deployment? Others have those skills.

It's been well over 10 years we've been proclaiming that any good
solution might take (gasp) as long as 10 years to deploy.

So let's just have this IFUSSP design, please. Or let's stop claiming
it exists.

-- 
        -Barry Shein

The World              | bzs@TheWorld.com           | http://www.TheWorld.com
Purveyors to the Trade | Voice: 800-THE-WRLD        | Login: Nationwide
Software Tool & Die    | Public Access Internet     | SINCE 1989     *oo*

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