Re: [Asrg] draft-irtf-asrg-criteria (was Re: request for review for a non FUSSP proposal)
Ian Eiloart <iane@sussex.ac.uk> Fri, 26 June 2009 15:34 UTC
Return-Path: <iane@sussex.ac.uk>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B2DCD3A68B9 for <asrg@core3.amsl.com>; Fri, 26 Jun 2009 08:34:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level:
X-Spam-Status: No, score=-2.119 tagged_above=-999 required=5 tests=[AWL=-0.319, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uyqEzUXNkXMd for <asrg@core3.amsl.com>; Fri, 26 Jun 2009 08:34:39 -0700 (PDT)
Received: from karpinski.uscs.susx.ac.uk (karpinski.uscs.susx.ac.uk [139.184.14.85]) by core3.amsl.com (Postfix) with ESMTP id 9FECC3A6922 for <asrg@irtf.org>; Fri, 26 Jun 2009 08:34:39 -0700 (PDT)
Received: from lewes.staff.uscs.susx.ac.uk ([139.184.134.43]:63786) by karpinski.uscs.susx.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.64) (envelope-from <iane@sussex.ac.uk>) id KLUQDS-000JKF-CF for asrg@irtf.org; Fri, 26 Jun 2009 16:15:28 +0100
Date: Fri, 26 Jun 2009 16:14:38 +0100
From: Ian Eiloart <iane@sussex.ac.uk>
Sender: iane@sussex.ac.uk
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Message-ID: <85578757E72FE7CC2CEA4753@lewes.staff.uscs.susx.ac.uk>
In-Reply-To: <20090626144255.1D65724300@panix5.panix.com>
References: <4A43B696.2000106@cybernothing.org> <4A449A7C.6070106@tana.it> <20090626100736.GA29159@gsp.org> <9088C3969464C4F82C833994@lewes.staff.uscs.susx.ac.uk> <20090626141149.CDEEF24300@panix5.panix.com> <D69914E05B16AC021650F34A@lewes.staff.uscs.susx.ac.uk> <20090626144255.1D65724300@panix5.panix.com>
Originator-Info: login-token=Mulberry:01iwtc5/RsykzMeLBJ9zH+gM9a8YN9Qe4xAHY=; token_authority=support@its.sussex.ac.uk
X-Mailer: Mulberry/4.0.8 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Sussex: true
X-Sussex-transport: remote_smtp
Subject: Re: [Asrg] draft-irtf-asrg-criteria (was Re: request for review for a non FUSSP proposal)
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jun 2009 15:34:40 -0000
--On 26 June 2009 10:42:55 -0400 Seth <sethb@panix.com> wrote: > Ian Eiloart <iane@sussex.ac.uk> wrote: >> --On 26 June 2009 10:11:49 -0400 Seth <sethb@panix.com> wrote: >>> Ian Eiloart <iane@sussex.ac.uk> wrote: >>> >>>> Frankly, I don't like that definition. Specifically it misses an >>>> important class of spam - well targeted, individualised, unsolicited >>>> marketing messages which are necessarily unique (and hence not >>>> bulk). >>> >>> What makes them unique? If the individualisation is merely a mail >>> merge, they're still bulk. If the salescritter spent an hour >>> investigating me in order to determine that I'm a good prospect and >>> figure out the best way to entice me, the problem scales just fine. >> >> And how would I, as a recipient, know which had happened? How would >> I know whether to report the message as spam? > > If it isn't apparent from the message itself, you probably shouldn't > be on the net without adult supervision. Really, SMTP has some feature that lets me determine -from the content of an email- exactly how that email was constructed and who spent what amount of time putting it together? Neat. Is that in RFC 2821 of 2822. Must be 2822, since you said "from the message itself". Well, there's our solution then. We just need to examine the content of the X-i-struggled-for-half-an-hour-to-discover-whether-you'd-be-likely-to-be-interested-in-this-offer header. > Seth > _______________________________________________ > Asrg mailing list > Asrg@irtf.org > http://www.irtf.org/mailman/listinfo/asrg -- Ian Eiloart IT Services, University of Sussex 01273-873148 x3148 For new support requests, see http://www.sussex.ac.uk/its/help/
- [Asrg] draft-irtf-asrg-criteria (was Re: request … J.D. Falk
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Douglas Otis
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Alessandro Vesely
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Rich Kulawiec
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Ian Eiloart
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Ian Eiloart
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Alessandro Vesely
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Ian Eiloart
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Seth
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Seth
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Ian Eiloart
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Seth
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… der Mouse
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… der Mouse
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Ian Eiloart
- Re: [Asrg] draft-irtf-asrg-criteria is missing Ou… Ian Eiloart
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Seth
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Alessandro Vesely
- Re: [Asrg] draft-irtf-asrg-criteria is missing Ou… Douglas Otis
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… J.D. Falk
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Douglas Otis
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Alessandro Vesely
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Claudio Telmon
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Dave CROCKER
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Claudio Telmon
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Michael Thomas
- Re: [Asrg] No, we're not going to define spam John Levine
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Ian Eiloart
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Ian Eiloart
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Alessandro Vesely
- Re: [Asrg] No, we're not going to define spam Alessandro Vesely
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Claudio Telmon
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Rich Kulawiec
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Alessandro Vesely
- Re: [Asrg] draft-irtf-asrg-criteria is missing Ou… Douglas Otis
- Re: [Asrg] really, we're not going to define spam… John Levine
- Re: [Asrg] draft-irtf-asrg-criteria is missing Ou… Danny Angus
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Danny Angus
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Steve Atkins
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Seth
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Claudio Telmon
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Alessandro Vesely
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Claudio Telmon
- Re: [Asrg] draft-irtf-asrg-criteria is missing Ou… Douglas Otis
- Re: [Asrg] draft-irtf-asrg-criteria (was Re: requ… Danny Angus
- Re: [Asrg] draft-irtf-asrg-criteria is missing Ou… Danny Angus