RE: [Asrg] C/R - What people say

"Eric Dean" <eric@purespeed.com> Thu, 15 May 2003 13:41 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 JAA08644 for <asrg-archive@odin.ietf.org>; Thu, 15 May 2003 09:41:00 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4FD81o32241 for asrg-archive@odin.ietf.org; Thu, 15 May 2003 09:08:01 -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 h4FD81B32238 for <asrg-web-archive@optimus.ietf.org>; Thu, 15 May 2003 09:08:01 -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 JAA08625; Thu, 15 May 2003 09:40:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19GJ04-0007Ju-00; Thu, 15 May 2003 09:42:24 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19GJ03-0007Jq-00; Thu, 15 May 2003 09:42:23 -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 h4FD23B31126; Thu, 15 May 2003 09:02:03 -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 h4FD1GB31081 for <asrg@optimus.ietf.org>; Thu, 15 May 2003 09:01:16 -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 JAA08476 for <asrg@ietf.org>; Thu, 15 May 2003 09:33:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19GItX-0007IW-00 for asrg@ietf.org; Thu, 15 May 2003 09:35:39 -0400
Received: from ns2.tidalwave.net ([66.77.68.8] helo=mailgate.purespeed.com) by ietf-mx with esmtp (Exim 4.12) id 19GItW-0007IL-00 for asrg@ietf.org; Thu, 15 May 2003 09:35:38 -0400
Received: from purespeed.com (mail.purespeed.com [66.77.69.8]) by mailgate.purespeed.com (Postfix Relay Hub) with ESMTP id B9E771396D; Thu, 15 May 2003 09:38:51 -0400 (EDT)
Received: from HOMEY [68.100.19.195] by purespeed.com (SMTPD32-7.13) id A7D03164002C; Thu, 15 May 2003 09:36:16 -0400
From: Eric Dean <eric@purespeed.com>
To: Vernon Schryver <vjs@calcite.rhyolite.com>, asrg@ietf.org
Subject: RE: [Asrg] C/R - What people say
Message-ID: <MBEKIIAKLDHKMLNFJODBCEAHFDAA.eric@purespeed.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
In-Reply-To: <200305150242.h4F2gu3k017638@calcite.rhyolite.com>
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: Thu, 15 May 2003 09:38:33 -0400
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> I think that's an overstatement or beside the point.  While according
> to standards theory, Sender: headers may have nothing to do with
> whether the message is bulk, practice may differ.  I'd want to look
> at a few 1,000,000 private messages in a variety of locations and
> check the behavior of a bunch of MTAs and MUAs before guessing whether
> in practice "Sender" headers indicate "bulk."

Considering that we are a research group and not a standard's group, that
would be an excellent approach.  We've found that the Sender header works in
many cases but many people pointed out additional methods...this isn't a
trivial issue.

> > From: "Eric Dean" <eric@purespeed.com>
>
> > ok..very nice..so what do you propose for list detection?
>
> It's not Dave Crocker's fault that Sender headers do not necessarily
> indcate "bulk," and neither is it his responsibility to find a solution
> to your problem if they don't.

>  You could but don't absolutely need to
> thank him for pointing out a hole.

Thanks Dave

> You certainly should not snarl.

Indeed...I did snarl as I wrote that response.

> In your position, I'd hope to offer evidence showing that in practice
> Sender: headers do work or some (real, not invented) words in an RFC
> showing that Dave Crocker is mistaken.  Failing that, I'd probably
> fall back on "well, C/R isn't perfect, but it's good enough to help"
> (if that were my opinion, which it isn't).

Well, I believe there is more work to be done in this area.  We use Sender
but it appears that many other mechanisms are available..yet nothing
standard.



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