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

"Peter Kay" <peter@titankey.com> Wed, 04 June 2003 18:36 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 OAA05367 for <asrg-archive@odin.ietf.org>; Wed, 4 Jun 2003 14:36:20 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h54IZtc08322 for asrg-archive@odin.ietf.org; Wed, 4 Jun 2003 14:35:55 -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 h54IZtB08319 for <asrg-web-archive@optimus.ietf.org>; Wed, 4 Jun 2003 14:35:55 -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 OAA05359; Wed, 4 Jun 2003 14:35:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Nd5E-0006bb-00; Wed, 04 Jun 2003 14:34:00 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Nd5D-0006bY-00; Wed, 04 Jun 2003 14:33:59 -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 h54IX6B08226; Wed, 4 Jun 2003 14:33:06 -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 h54IWUB08197 for <asrg@optimus.ietf.org>; Wed, 4 Jun 2003 14:32:30 -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 OAA05259 for <asrg@ietf.org>; Wed, 4 Jun 2003 14:32:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Nd1v-0006ak-00 for asrg@ietf.org; Wed, 04 Jun 2003 14:30:35 -0400
Received: from imail.centuryc.net ([216.30.168.20] helo=isp-appsvr01.centuryc.com) by ietf-mx with esmtp (Exim 4.12) id 19Nd1u-0006aH-00 for asrg@ietf.org; Wed, 04 Jun 2003 14:30:34 -0400
Received: from cybercominc.com [66.91.134.126] by isp-appsvr01.centuryc.com (SMTPD32-7.14) id AB752ED0096; Wed, 04 Jun 2003 08:33:25 -1000
Received: from a66b91n134client123.hawaii.rr.com (66.91.134.123) by cybercominc-zzt with SMTP; Wed, 04 Jun 2003 18:36:31 GMT
X-Titankey-e_id: <7eac0708-9741-421b-905a-204d94c0cab0>
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: RE: [Asrg] Another criteria for "what is spam"...
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Message-ID: <DD198B5D07F04347B7266A3F35C42B0B0FD01F@io.cybercom.local>
Thread-Topic: [Asrg] Another criteria for "what is spam"...
Thread-Index: AcMqbC/U5uSL5+hxSm6+27aZ6X6GaQAWMrdQ
From: Peter Kay <peter@titankey.com>
To: Dave Crocker <dcrocker@brandenburg.com>, Barry Shein <bzs@world.std.com>
Cc: asrg@ietf.org
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h54IWUB08198
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:31:57 -1000
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


> 
> My personal favorite definition, these days, is
> 
>    Unsolicited Bulk Mail (UBE)
>    

This is good, short and simple.  

> 
> And we need to define bulk properly. This will be difficult. 
> If I send an unsolicited message to 2 people, does it 
> qualify? What about 10 people, 100, 1000? Why? Why not?
> 

To me, BULK email is email which is programmatically sent out to > 1
person. Programmatically here means by means of automated systems, i.e.
mailmerge processes. So, yes, if I do a copy/paste of my entire contact
list, paste them in my email, and announce my new company, I'm doing
bulk email.   

> So we then need to define unsolicited properly. We must make 
> sure to permit me to make contact with someone for the first 
> time. Not all cold calls are bad; in fact they are essential 
> to many desirable aspects of social intercourse. We need to 
> make sure that we define "permission" properly -- as a kind 
> of opposite to unsolicited -- and so we can then enjoy 
> wonderful debates about details such as double opt-in. And so 
> on. Still, I think the question of "unsolicited" is 
> well-enough understood to make it possible to get community 
> rough consensus on a technical definition that the 
> engineering community can work with.
> 

A definition of UNSOLICITED, I believe, is the core of the issue and the
problem, primarily because it will force us to address the eye of the
storm: 

is Internet email inherently trusted or is it untrusted?

Is email considered unsolicited until the recipient decides it is
solicited? Or is it considered solicited until the recipient decides it
is unsolicited?

I think this is the big question, ladies.

And I would say that today's spam problem is because SMTP was born in an
environment where email was inherently trusted. SMTP protocol is AWASH
with trusted processes.  Not the least of which is clear text
transmission.

But because the Internet went commercial, suddenly SMTP found itself in
an environment where email (IMHO) is inherently untrusted.  And spam is
what you get when you put a protocol meant for scholars and scientists
in the hands of capitalists.

Peter


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