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

Elric Pedder <elric@novitraq.com> Sat, 21 June 2003 04:27 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 AAA19470 for <asrg-archive@odin.ietf.org>; Sat, 21 Jun 2003 00:27:35 -0400 (EDT)
Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5L4R8k10545 for asrg-archive@odin.ietf.org; Sat, 21 Jun 2003 00:27:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TZy0-0002k0-Bc for asrg-web-archive@optimus.ietf.org; Sat, 21 Jun 2003 00:27:08 -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 AAA19463; Sat, 21 Jun 2003 00:27:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19TZxx-0005br-00; Sat, 21 Jun 2003 00:27:05 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19TZxx-0005bo-00; Sat, 21 Jun 2003 00:27:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TZxt-0002i5-8i; Sat, 21 Jun 2003 00:27:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TZxm-0002hu-5i for asrg@optimus.ietf.org; Sat, 21 Jun 2003 00:26:54 -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 AAA19458 for <asrg@ietf.org>; Sat, 21 Jun 2003 00:26:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19TZxj-0005bl-00 for asrg@ietf.org; Sat, 21 Jun 2003 00:26:51 -0400
Received: from dns.novitraq.com ([204.92.85.2] helo=novitraq.com) by ietf-mx with smtp (Exim 4.12) id 19TZxj-0005bh-00 for asrg@ietf.org; Sat, 21 Jun 2003 00:26:51 -0400
Received: from ([24.200.195.55]) by novitraq.com with WebMail (Mailtraq/2.3.0.1402) id NVTRD7185DFF Sat, 21 Jun 2003 00:23:40 -0400
Subject: Re: [Asrg] New proposal for spam blocking: Greylisting
From: Elric Pedder <elric@novitraq.com>
To: asrg@ietf.org
X-Client-Ip: 24.200.195.55
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Message-ID: <NVTRD7185DFF@novitraq.com>
In-Reply-To: <a05200f09bb193252834d@[10.0.1.19]>
References: <a05200f09bb193252834d@[10.0.1.19]> <Pine.LNX.4.44.0306201317531.8633-100000@kinison.puremagic.com>
X-Hops: 1
Content-Transfer-Encoding: 7bit
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: Sat, 21 Jun 2003 00:23:40 -0400
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

John Morris in <a05200f09bb193252834d@[10.0.1.19]>

> At 1:24 PM -0500 6/20/03, Evan Harris wrote:

[snip]

> >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.

If only a hash of the triplet were stored, would this solve
the privacy issue?

Regard,
      - Elric

-- 
Elric Pedder
Mailtraq Development (www.mailtraq.com)


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