Re: [Asrg] Adding a spam button to MUAs

Steve Atkins <> Mon, 01 February 2010 17:10 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B67C03A67E3 for <>; Mon, 1 Feb 2010 09:10:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.443
X-Spam-Status: No, score=-6.443 tagged_above=-999 required=5 tests=[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 UhShSa66VYy0 for <>; Mon, 1 Feb 2010 09:10:47 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id A23923A67AB for <>; Mon, 1 Feb 2010 09:10:47 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id A948380295 for <>; Mon, 1 Feb 2010 09:11:17 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1077)
From: Steve Atkins <>
In-Reply-To: <>
Date: Mon, 1 Feb 2010 09:11:15 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <>
To: Anti-Spam Research Group - IRTF <>
X-Mailer: Apple Mail (2.1077)
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 17:10:48 -0000

On Feb 1, 2010, at 8:57 AM, Ian Eiloart wrote:

> --On 1 February 2010 14:59:03 +0000 John Levine <> wrote:
>> 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.
> So, are we looking at an IMAP/ANNOTATE extension for IMAP users and an RFC5451 modification for SMTP users? The IMAP/ANNOTATE is much more efficient than sending an abuse report, and less susceptible to outside interference.
> Does ARF allow richer expression than ANNOTATE?

Probably - it's basically a container format.

More importantly, perhaps, it would be easy to roll out on existing installations with a trivial configuration change, rather than requiring functionality in the mailstore that may not be there.

It also doesn't require anything more of the MUA other than the ability to construct and send a basic MIME email, and works identically for mail retrieved via IMAP, POP, SQL, HTTP, mbox, maildir or any of the other obscure ways people access their mail stores.

As for efficiency, I was picturing two variants of the header - one which sends a copy of the entire email, and so doesn't require any shared state between client and mailstore, and one which sends back just the contents of the header (which could include a message-id, an IMAP UID or some system specific primary key).