Re: [Asrg] Spam button scenarios

Steve Atkins <steve@blighty.com> Mon, 08 February 2010 20:23 UTC

Return-Path: <steve@blighty.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 134C63A7288 for <asrg@core3.amsl.com>; Mon, 8 Feb 2010 12:23:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.458
X-Spam-Level:
X-Spam-Status: No, score=-6.458 tagged_above=-999 required=5 tests=[AWL=-0.015, 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 TsGtRsOoXl-I for <asrg@core3.amsl.com>; Mon, 8 Feb 2010 12:23:44 -0800 (PST)
Received: from m.wordtothewise.com (fruitbat.wordtothewise.com [208.187.80.135]) by core3.amsl.com (Postfix) with ESMTP id 5791E28C10B for <asrg@irtf.org>; Mon, 8 Feb 2010 12:23:44 -0800 (PST)
Received: from platter.wordtothewise.com (184.wordtothewise.com [208.187.80.184]) by m.wordtothewise.com (Postfix) with ESMTP id 7DC3D80754 for <asrg@irtf.org>; Mon, 8 Feb 2010 12:24:47 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Apple Message framework v1077)
From: Steve Atkins <steve@blighty.com>
In-Reply-To: <4B7071D9.4080801@nortel.com>
Date: Mon, 08 Feb 2010 12:24:36 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <80383760-91CA-4E8B-812B-477B738BD594@blighty.com>
References: <alpine.BSF.2.00.1002080111310.16135@simone.lan> <4B7071D9.4080801@nortel.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
X-Mailer: Apple Mail (2.1077)
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:23:45 -0000

On Feb 8, 2010, at 12:19 PM, Chris Lewis wrote:

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

Even though the mail was never received by Gmail, just fetched by them from the IMAP server it was delivered to?

If the reporting address is included in the AR header as added at the Yahoo MX, that would't be overwritten by Gmail, I don't think?

Cheers,
  Steve