Re: [Asrg] Adding a spam button to MUAs

"Chris Lewis" <> Mon, 01 February 2010 16:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AF01D28C1DB for <>; Mon, 1 Feb 2010 08:20:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.399
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 6c6HktL7fyJ4 for <>; Mon, 1 Feb 2010 08:20:52 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 377C728C15B for <>; Mon, 1 Feb 2010 08:20:51 -0800 (PST)
Received: from ( []) by (Switch-2.2.0/Switch-2.2.0) with ESMTP id o11GLBQ28804 for <>; Mon, 1 Feb 2010 16:21:11 GMT
Received: from ([]) by with Microsoft SMTPSVC(6.0.3790.3959); Mon, 1 Feb 2010 11:20:49 -0500
Received: from [] ( by ( with Microsoft SMTP Server (TLS) id 8.1.340.0; Mon, 1 Feb 2010 11:20:49 -0500
Message-ID: <>
Date: Mon, 1 Feb 2010 11:20:45 -0500
From: "Chris Lewis" <>
Organization: Nortel
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20090812 Lightning/0.9 Thunderbird/ Mnenhy/
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <>
References: <> <>
In-Reply-To: <>
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-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <>
List-Id: Anti-Spam Research Group - IRTF <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-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.