Re: [Asrg] New proposal for spam blocking: Greylisting

John Morris <jmorris@cdt.org> Fri, 20 June 2003 22:08 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 SAA11828 for <asrg-archive@odin.ietf.org>; Fri, 20 Jun 2003 18:08:30 -0400 (EDT)
Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5KM83a25565 for asrg-archive@odin.ietf.org; Fri, 20 Jun 2003 18:08:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TU39-0006eG-TA for asrg-web-archive@optimus.ietf.org; Fri, 20 Jun 2003 18:08:03 -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 SAA11756; Fri, 20 Jun 2003 18:07:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19TU37-0003s9-00; Fri, 20 Jun 2003 18:08:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19TU36-0003s6-00; Fri, 20 Jun 2003 18:08:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TU37-0006ZE-JM; Fri, 20 Jun 2003 18:08:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TU2k-0006Xi-0H for asrg@optimus.ietf.org; Fri, 20 Jun 2003 18:07:38 -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 SAA11706 for <asrg@ietf.org>; Fri, 20 Jun 2003 18:07:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19TU2h-0003rY-00 for asrg@ietf.org; Fri, 20 Jun 2003 18:07:35 -0400
Received: from mail.cdt.org ([206.112.85.61]) by ietf-mx with esmtp (Exim 4.12) id 19TU2g-0003rM-00 for asrg@ietf.org; Fri, 20 Jun 2003 18:07:34 -0400
Received: from [10.0.1.19] (66.safeclick.net [63.119.245.66]) by mail.cdt.org (Postfix) with ESMTP id B26B44900DB for <asrg@ietf.org>; Fri, 20 Jun 2003 18:05:44 -0400 (EDT)
Mime-Version: 1.0
X-Sender: john@mail.cdt.org
Message-Id: <a05200f09bb193252834d@[10.0.1.19]>
In-Reply-To: <Pine.LNX.4.44.0306201317531.8633-100000@kinison.puremagic.com>
References: <Pine.LNX.4.44.0306201317531.8633-100000@kinison.puremagic.com>
To: asrg@ietf.org
From: John Morris <jmorris@cdt.org>
Subject: Re: [Asrg] New proposal for spam blocking: Greylisting
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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: Fri, 20 Jun 2003 18:07:33 -0400

At 1:24 PM -0500 6/20/03, Evan Harris wrote:
>  > > I would agree that users should be made aware of any possible 
>privacy risks,
>>  > but most users are already aware that mailer level statistics 
>>are kept, and
>>  > this is just the same thing, just a different format.
>>
>>  That mailer logs are also quite sensitive does not make your records
>>  less sensitive.
>
>The only issue I had with the original statement was the claim that this
>method should cause greater concern for privacy.  While there are privacy
>concerns with any statistics, I wouldn't consider this method any more of a
>danger than normal server logs, since nothing is kept that couldn't be found
>there.
>
>Evan

FWIW, my original point was that the grey list approach is a greater 
cause for concern than a simple white list approach (which can reveal 
a user's correspondents but not the date and time of the first and 
last e-mail and the number of successful e-mails).

I agree that the grey  list approach is not radically more 
problematic than mail server logs.  But even on that point, having 
two places where private info aggregates is worse than having one.

Moreover, the greylist might in some cases be easier to locate or 
access -- in some situations, for example a civil litigant might have 
fairly direct access to his or her grey list (and thus be easily 
required to produce it), but the related mail server logs might be 
held by a third party ISP not under the litigant's control.  And, 
once produced, the greylist can serve as an incomplete but still 
useful index into the mail server logs.

By pressing these points, I am not intending to be negative toward 
the proposal -- it certainly looks to be worth exploring further. 
But, when stacking this up against some of the other ideas and 
proposals, I think it is unavoidable that this has greater privacy 
implications than some other approaches.  Now if it is also 
significantly more effective, then greylists may well be worth the 
greater privacy risk (and there may be techniques that can reduce the 
privacy risks, such as the use of one way hashes of the triplets).

John

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