Re: RE: [Asrg] C/R Thoughts: Take 1

"Jon Kyme" <jrk@merseymail.com> Wed, 14 May 2003 21:12 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 RAA05806 for <asrg-archive@odin.ietf.org>; Wed, 14 May 2003 17:12:40 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4EKdL417389 for asrg-archive@odin.ietf.org; Wed, 14 May 2003 16:39:21 -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 h4EKdLB17386 for <asrg-web-archive@optimus.ietf.org>; Wed, 14 May 2003 16:39:21 -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 RAA05788; Wed, 14 May 2003 17:12:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19G3Zd-0001Pl-00; Wed, 14 May 2003 17:14:05 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19G3Zc-0001Pi-00; Wed, 14 May 2003 17:14:04 -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 h4EKbPB17198; Wed, 14 May 2003 16:37:25 -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 h4EKaRB16405 for <asrg@optimus.ietf.org>; Wed, 14 May 2003 16:36:27 -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 RAA05712 for <asrg@ietf.org>; Wed, 14 May 2003 17:09:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19G3Wp-0001Oh-00 for asrg@ietf.org; Wed, 14 May 2003 17:11:11 -0400
Received: from argon.connect.org.uk ([193.110.243.33]) by ietf-mx with esmtp (Exim 4.12) id 19G3Wo-0001OZ-00 for asrg@ietf.org; Wed, 14 May 2003 17:11:10 -0400
Received: from mmail by argon.connect.org.uk with local (connectmail/exim) id 19G3Xn-0005KL-00; Wed, 14 May 2003 22:12:11 +0100
In-Reply-To: <5.2.0.9.2.20030514133033.00b335a8@std5.imagineis.com>
Subject: Re: RE: [Asrg] C/R Thoughts: Take 1
To: Yakov Shafranovich <research@solidmatrix.com>
From: Jon Kyme <jrk@merseymail.com>
Cc: ASRG <asrg@ietf.org>
X-Mailer: [ConnectMail 3.5.4]
X-connectmail-Originating-IP: 158.152.118.31
Message-Id: <E19G3Xn-0005KL-00@argon.connect.org.uk>
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, 14 May 2003 22:12:11 +0100

> If Spam-Arrest
> >operated in the EU, its operation would be illegal (not the
> anti-spamming
> >law, the data protection laws) 

I believe this is correct.


> 
> The point I was trying to make is that from the technical viewpoint any
> ISP
> or MTA operator can harvest addresses just like SpamArrest did.
> 


yes, of course. The point I was trying to make is that these concerns
should perhaps be addressed in any work to produce standards or BCP on C/R

Most MTA operators only keep "traffic data" for a short time. A C/R
operator must keep some traffic data "forever".

The C/R operator can choose from a range of behaviours ... producing a
simple challenge, puffing the challenge up with unsolicited merchandising
material right up to using (or selling) addresses like any other spammer.

Since the Sender address data is longlived, the policy might change -
imagine Mr Nice C/R systems Inc. gets bought up by Black hat Megacorp.

Whatever..




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