Re: [Asrg] Spam button scenarios

"Chris Lewis" <clewis@nortel.com> Mon, 08 February 2010 20:18 UTC

Return-Path: <CLEWIS@nortel.com>
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 F31433A7368 for <asrg@core3.amsl.com>; Mon, 8 Feb 2010 12:18:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.46
X-Spam-Level:
X-Spam-Status: No, score=-6.46 tagged_above=-999 required=5 tests=[AWL=-0.017, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SUBJECT_FUZZY_TION=0.156]
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 3vmarYBFkrq0 for <asrg@core3.amsl.com>; Mon, 8 Feb 2010 12:18:57 -0800 (PST)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id DD88D3A682A for <asrg@irtf.org>; Mon, 8 Feb 2010 12:18:56 -0800 (PST)
Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id o18KJuq28179 for <asrg@irtf.org>; Mon, 8 Feb 2010 20:19:57 GMT
Received: from zrtphx5h0.corp.nortel.com ([47.140.202.65]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 8 Feb 2010 15:19:56 -0500
Received: from [47.130.64.86] (47.130.64.86) by zrtphx5h0.corp.nortel.com (47.140.202.65) with Microsoft SMTP Server (TLS) id 8.1.340.0; Mon, 8 Feb 2010 15:19:56 -0500
Message-ID: <4B7071D9.4080801@nortel.com>
Date: Mon, 8 Feb 2010 15:19:37 -0500
From: "Chris Lewis" <clewis@nortel.com>
Organization: Nortel
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23) Gecko/20090812 Lightning/0.9 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <alpine.BSF.2.00.1002080111310.16135@simone.lan>
In-Reply-To: <alpine.BSF.2.00.1002080111310.16135@simone.lan>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Feb 2010 20:19:56.0665 (UTC) FILETIME=[14BD3690:01CAA8FC]
Subject: Re: [Asrg] Spam button scenarios
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: Mon, 08 Feb 2010 20:18:58 -0000

John R. Levine wrote:
> Here's some scenarios in which I'm not sure what the best thing is to do.
> 
> A) User has multiple incoming accounts, presses the spam button, and the 
> outbound MSA doesn't match the incoming account.  Hence the report goes 
> via unrelated third parties that might snoop on it.  Do we care?  The user 
> has said it's spam, after all.

I'm leaning back towards inband (eg: RFC5451 AR header as extended), 
thus your B is moot, and addressing choices (sans trust issues) is trivial.

> C) I have a Gmail account and a Yahoo account.  The Gmail account is set 
> up to fetch my Yahoo mail so I can see it all in one place.  I use Gmail's 
> IMAP server to read my mail.  (I really do this, by the way.)  I hit the 
> spam button.  Who should get the report?

>   1) Gmail since that's who I picked it up from
>   2) Yahoo since that's where the spam was sent
>   3) Gmail but they should also forward the report to Yahoo

Very much Gmail.  If they want to chain it back to Yahoo as part of 
their FBL, they can.