Re: [Asrg] Another criteria for "what is spam"...

Vernon Schryver <vjs@calcite.rhyolite.com> Wed, 04 June 2003 14:10 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 KAA21305 for <asrg-archive@odin.ietf.org>; Wed, 4 Jun 2003 10:10:45 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h54EAKC18959 for asrg-archive@odin.ietf.org; Wed, 4 Jun 2003 10:10:20 -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 h54EAKB18956 for <asrg-web-archive@optimus.ietf.org>; Wed, 4 Jun 2003 10:10:20 -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 KAA21244; Wed, 4 Jun 2003 10:10:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NYwE-00038a-00; Wed, 04 Jun 2003 10:08:26 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19NYwD-00038X-00; Wed, 04 Jun 2003 10:08:25 -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 h54E34B17710; Wed, 4 Jun 2003 10:03:04 -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 h54E2HB17673 for <asrg@optimus.ietf.org>; Wed, 4 Jun 2003 10:02:17 -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 KAA20181 for <asrg@ietf.org>; Wed, 4 Jun 2003 10:02:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NYoR-00030P-00 for asrg@ietf.org; Wed, 04 Jun 2003 10:00:23 -0400
Received: from calcite.rhyolite.com ([192.188.61.3]) by ietf-mx with esmtp (Exim 4.12) id 19NYoP-000309-00 for asrg@ietf.org; Wed, 04 Jun 2003 10:00:22 -0400
Received: (from vjs@localhost) by calcite.rhyolite.com (8.12.10.Beta0/8.12.10.Beta0) id h54E28A7010799 for asrg@ietf.org env-from <vjs>; Wed, 4 Jun 2003 08:02:08 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200306041402.h54E28A7010799@calcite.rhyolite.com>
To: asrg@ietf.org
Subject: Re: [Asrg] Another criteria for "what is spam"...
References: <83219933227.20030603234722@brandenburg.com>
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: Wed, 04 Jun 2003 08:02:08 -0600

> From: Dave Crocker <dhc@dcrocker.net>

> ...
> Imagine a student who is researching a paper and hears about a number of
> different people who might have relevant knowledge.

> ...
> The student sends the same query for assistance to each of these people.
> It does not matter whether the student sends a different copy (with the
> same text) to each recipient or puts all of the recipients into the
> address list of the same.
>
> And there are many reasonable examples of scenarios, like this, which
> qualify as spam, according to your definition, but would not qualify as
> spam to the general community of email users.

The error in that is common.  You are construing "unsolicited bulk email"
as if it were an aritimetic formula, effectively computable algorithm (the
formal notion related to "Turing computable"), or a statement in a first
order predicate calculus instead of a law or rule among people.

Consider the legal notion of "burglary."  It is not a first order
logical predicate but what a "reasonable person" sees as being in the
wrong place without permission and with bad intentions.  The fuzziness
of "wrong place," "permission," and "malice" is intentional and vital
and not a bug.

Look at "cracking" or "security attack."   There is no confusion there
(at least among us) despite the fact that the same set of packets can
be benign or an attack depending on circumstances.  We each act as
the legal word's notion of a "reasonable person" in that area.

If the student's query were "solicited" by its targets, then it would
not be "unsolicted bulk email."  If it were not solicited and it
involved what a reasonable person would consider lots of mail, then
it would be "unsolicited bulk email."   That "unsolicited" and "bulk"
are not defined legalistically and as a number is a feature instead
of a bug for the same reason that you don't say that every strange
UDP packet a "port scan."

It's odd how many people who are "reasonable" in the legal sense of
a "reasonable person" when confronted with a tcpdump trace or some
real mail but when talking about spam definitions turn into either
GFWs or Richard Stallmans of the 1980s demanding the inalienable right
to use any and all unused CPU cycles and disk space on other people's
computers.

(GFWs or "Goobers with firewalls" are experts with "personal firewalls"
who report "hacking" from the root's DNS servers.)


Vernon Schryver    vjs@rhyolite.com
_______________________________________________
Asrg mailing list
Asrg@ietf.org
https://www1.ietf.org/mailman/listinfo/asrg