Re: [Asrg] Adding a spam button to MUAs

Bart Schaefer <schaefer@brasslantern.com> Mon, 01 February 2010 17:24 UTC

Return-Path: <schaefer@closedmail.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 1F36B28C219 for <asrg@core3.amsl.com>; Mon, 1 Feb 2010 09:24:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.443
X-Spam-Level:
X-Spam-Status: No, score=-2.443 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 px+S2AOKLR0m for <asrg@core3.amsl.com>; Mon, 1 Feb 2010 09:24:01 -0800 (PST)
Received: from vms173015pub.verizon.net (vms173015pub.verizon.net [206.46.173.15]) by core3.amsl.com (Postfix) with ESMTP id 7B31028C18C for <asrg@irtf.org>; Mon, 1 Feb 2010 09:23:13 -0800 (PST)
Received: from torch.brasslantern.com ([unknown] [173.67.92.79]) by vms173015.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0KX600E9IAZ3J32C@vms173015.mailsrvcs.net> for asrg@irtf.org; Mon, 01 Feb 2010 11:23:32 -0600 (CST)
Received: from torch.brasslantern.com (localhost.localdomain [127.0.0.1]) by torch.brasslantern.com (8.13.1/8.13.1) with ESMTP id o11HNQN6005489 for <asrg@irtf.org>; Mon, 01 Feb 2010 09:23:27 -0800
Received: (from schaefer@localhost) by torch.brasslantern.com (8.13.1/8.13.1/Submit) id o11HNQ4V005488 for asrg@irtf.org; Mon, 01 Feb 2010 09:23:26 -0800
From: Bart Schaefer <schaefer@brasslantern.com>
Message-id: <100201092326.ZM5487@torch.brasslantern.com>
Date: Mon, 01 Feb 2010 09:23:25 -0800
In-reply-to: <A50C736E-EE14-4213-B99D-DD58C669FDAC@blighty.com>
Comments: In reply to Steve Atkins <steve@blighty.com> "Re: [Asrg] Adding a spam button to MUAs" (Feb 1, 9:11am)
References: <20100201145903.30670.qmail@simone.iecc.com> <3741B85B916D847C703F2724@lewes.staff.uscs.susx.ac.uk> <A50C736E-EE14-4213-B99D-DD58C669FDAC@blighty.com>
X-Mailer: OpenZMail Classic (0.9.2 24April2005)
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
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 17:24:02 -0000

On Feb 1,  9:11am, Steve Atkins wrote:
}
} On Feb 1, 2010, at 8:57 AM, Ian Eiloart wrote:
} 
} > 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.

Anything that's going to be added as metadata to the message header
needs to be carefully specified so that a client that understands the
format can reside behind a server that does not.  E.g., depending on
where this metadata is added, one option might be to require a DKIM
signature to cover it.

Precisely because this would be rolled out on existing installations,
it's not sufficient to treat it like a Return-Path field and expect
the final delivery server to clean up any values that were improperly
inserted earlier in transit.

--