[Asrg] Spam button scenarios
"John R. Levine" <johnl@iecc.com> Mon, 08 February 2010 06:28 UTC
Return-Path: <johnl@iecc.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 A5FA73A6B62 for <asrg@core3.amsl.com>; Sun, 7 Feb 2010 22:28:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.29
X-Spam-Level:
X-Spam-Status: No, score=-9.29 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, RDNS_DYNAMIC=0.1, 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 t1M6AdnmKY7E for <asrg@core3.amsl.com>; Sun, 7 Feb 2010 22:28:01 -0800 (PST)
Received: from gal.iecc.com (64.57.183.53.lightlink.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id AE8193A69AA for <asrg@irtf.org>; Sun, 7 Feb 2010 22:28:00 -0800 (PST)
Received: (qmail 89924 invoked from network); 8 Feb 2010 06:29:01 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:user-agent:cleverness; s=k1002; bh=AN33V26FYPejVdXy9lUsFLgokO98JBkUcHC+JqxMWxE=; b=lmnsd6fL8x/s5oSdQtMdfjlDjtZvntVl0C9TAVR4dh3KskqchWPL/N7k9XwWKgdwehmI/BJ0Yhx+HV6grjUCDqgvK8O4t6n8Eq1cwEMQURuY6uOyupSMq4exlDFgdmGgmnI6yf8GzTWltkMq3//fek2jMeNaKWzBWMfYGB5xGPg=
Received: (ofmipd 208.31.42.62) with (DHE-RSA-AES256-SHA encrypted) SMTP; 8 Feb 2010 06:28:38 -0000
Date: Mon, 08 Feb 2010 01:28:59 -0500
Message-ID: <alpine.BSF.2.00.1002080111310.16135@simone.lan>
From: "John R. Levine" <johnl@iecc.com>
To: Anti Spam Research Group <asrg@irtf.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format="flowed"; charset="US-ASCII"
Subject: [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 06:28:06 -0000
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. B) Assume a model in which the spam reporting address is determined per account, e.g., fetched from the POP or IMAP server via an extension. The user for whatever reason moves a message from account A into the IMAP mailbox for account B and then hits the spam button, which sends the report to B, even though the message was from A. Do we care? It's the user's fault, although I can think of some simple configurations that would cause that, e.g., MUA based spam filter that puts all the junk into the Junk folder on the first IMAP account. 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 R's, John
- Re: [Asrg] Spam button scenarios Steve Atkins
- [Asrg] Spam button scenarios John R. Levine
- Re: [Asrg] Spam button scenarios Daniel Feenberg
- Re: [Asrg] Spam button scenarios Ian Eiloart
- Re: [Asrg] Spam button scenarios Andreas Saurwein Franci Gonçalves
- Re: [Asrg] Spam button scenarios John Levine
- Re: [Asrg] Spam button scenarios Ian Eiloart
- Re: [Asrg] Spam button scenarios Alessandro Vesely
- Re: [Asrg] Spam button scenarios Ian Eiloart
- Re: [Asrg] Spam button scenarios John Levine
- Re: [Asrg] Spam button scenarios Derek Diget
- Re: [Asrg] Spam button scenarios Martijn Grooten
- Re: [Asrg] Spam button scenarios der Mouse
- Re: [Asrg] Spam button scenarios Bill Weinman
- Re: [Asrg] Spam button scenarios Chris Lewis
- Re: [Asrg] Spam button scenarios Seth
- Re: [Asrg] Spam button scenarios Steve Atkins
- Re: [Asrg] Spam button scenarios Martijn Grooten
- Re: [Asrg] Spam button scenarios John Levine
- Re: [Asrg] Spam button scenarios Ian Eiloart
- Re: [Asrg] Spam button scenarios Ian Eiloart
- [Asrg] ARF traffic, was Spam button scenarios Alessandro Vesely
- Re: [Asrg] ARF traffic, was Spam button scenarios Steve Atkins
- Re: [Asrg] ARF traffic, was Spam button scenarios Ian Eiloart
- Re: [Asrg] ARF traffic, was Spam button scenarios Steve Atkins
- Re: [Asrg] ARF traffic, was Spam button scenarios Alessandro Vesely
- Re: [Asrg] ARF traffic, was Spam button scenarios Steve Atkins
- Re: [Asrg] ARF traffic, was Spam button scenarios Chris Lewis
- Re: [Asrg] ARF traffic, was Spam button scenarios Alessandro Vesely
- Re: [Asrg] ARF traffic, was Spam button scenarios Alessandro Vesely
- Re: [Asrg] ARF traffic, was Spam button scenarios Alessandro Vesely
- Re: [Asrg] ARF traffic, was Spam button scenarios Steve Atkins
- Re: [Asrg] ARF traffic, was Spam button scenarios Chris Lewis
- Re: [Asrg] ARF traffic, was Spam button scenarios Alessandro Vesely
- Re: [Asrg] ARF traffic, was Spam button scenarios Alessandro Vesely
- Re: [Asrg] ARF traffic, was Spam button scenarios Ian Eiloart
- Re: [Asrg] ARF traffic, was Spam button scenarios Ian Eiloart