Re: [Asrg] Adding a spam button to MUAs

"Chris Lewis" <clewis@nortel.com> Mon, 01 February 2010 16:20 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 AF01D28C1DB for <asrg@core3.amsl.com>; Mon, 1 Feb 2010 08:20:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.399
X-Spam-Level:
X-Spam-Status: No, score=-6.399 tagged_above=-999 required=5 tests=[AWL=0.044, 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 6c6HktL7fyJ4 for <asrg@core3.amsl.com>; Mon, 1 Feb 2010 08:20:52 -0800 (PST)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id 377C728C15B for <asrg@irtf.org>; Mon, 1 Feb 2010 08:20:51 -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 o11GLBQ28804 for <asrg@irtf.org>; Mon, 1 Feb 2010 16:21:11 GMT
Received: from zrtphx5h0.corp.nortel.com ([47.140.202.65]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 1 Feb 2010 11:20:49 -0500
Received: from [47.130.64.15] (47.130.64.15) by zrtphx5h0.corp.nortel.com (47.140.202.65) with Microsoft SMTP Server (TLS) id 8.1.340.0; Mon, 1 Feb 2010 11:20:49 -0500
Message-ID: <4B66FF5D.6040008@nortel.com>
Date: Mon, 1 Feb 2010 11:20:45 -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: <20100201145903.30670.qmail@simone.iecc.com> <C255A5EA-CECD-460B-B54B-A115D2C0FA6A@blighty.com>
In-Reply-To: <C255A5EA-CECD-460B-B54B-A115D2C0FA6A@blighty.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 Feb 2010 16:20:49.0989 (UTC) FILETIME=[848FEF50:01CAA35A]
Subject: Re: [Asrg] Adding a spam button to MUAs
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, 01 Feb 2010 16:20:53 -0000

Steve Atkins wrote:
> On Feb 1, 2010, at 6:59 AM, John Levine wrote:
> 
>>> Except that that isn't, I presume, the way these buttons currently
>>> work - except when somebody is subscribed to a feedback loop. It
>>> seems over-complicated and inefficient (even with BURL) to send an
>>> ARF to your own system admin, and rather more simple to just set a
>>> flag or annotation on the IMAP server.
>> You're right, for the minority of us who run IMAP.  For everyone else
>> who uses POP, mailing an ARF report back to the POP server may be the
>> best we can do.  The authserv-id from RFC 5451 isn't ideal to use as
>> the mailing address since the RFC says quite clearly that it has to
>> look like a FQDN but it doesn't actually have to be an FQDN.
>>
>> If we go down this route, we could probably add a flag to 5451 to
>> say it's OK to send ARF reports.
> 
> ... or put it in the the message, where there's one standard format
> to deal with, rather than tying it to just one of the various ways people 
> retrieve messages. Most everyone already stashes an assortment
> of metadata in the headers anyway.

Which gives you the opportunity to do more complicated things, like if 
the IMAP/POP servers aren't the place to send the notification.  In our 
case, they're not.

A X- header that has machine-readable instructions on what the reader 
should do if you hit the TiS button.

I'd envisage emailing ARF or plain forwards or site-chosen identifiers 
to a specified place.  Plus something non-SMTP.