Re: [Asrg] Adding a spam button to MUAs

John Levine <johnl@taugh.com> Mon, 01 February 2010 14:58 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 A211B3A693D for <asrg@core3.amsl.com>; Mon, 1 Feb 2010 06:58:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -19.043
X-Spam-Level:
X-Spam-Status: No, score=-19.043 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, RCVD_IN_DNSWL_HI=-8, 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 Gvx9MmT1d3WM for <asrg@core3.amsl.com>; Mon, 1 Feb 2010 06:58:30 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [208.31.42.53]) by core3.amsl.com (Postfix) with ESMTP id 6B4D63A6781 for <asrg@irtf.org>; Mon, 1 Feb 2010 06:58:30 -0800 (PST)
Received: (qmail 34690 invoked from network); 1 Feb 2010 14:59:03 -0000
Received: from mail1.iecc.com (208.31.42.56) by mail1.iecc.com with QMQP; 1 Feb 2010 14:59:03 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding; s=k1002; olt=johnl@user.iecc.com; bh=1pmJabpj2zMamAdQi4tqIzGrMIuLmjBLVHMW9aERGSE=; b=xdv5wb0eLqYu/hAoHqmKAh/RIojq+wBpG9zg9WIiRSK+lYAq+vOch6qLjvK8zyLqO61gbmPdFkFUusIb1J7J+1OW4EtiL1GwH9Ju5dUtiW6JLv6wLH+OW+OXB/HNQXws4rVMKXYoKo0rCQCP6d0h7UcQNFKch1PBq8oQDboft+E=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding; s=k1002; bh=1pmJabpj2zMamAdQi4tqIzGrMIuLmjBLVHMW9aERGSE=; b=LX6duaJahNCydRRUCC9DL28O+uuvf8pQyXenL6JGeROv0eQ1Y5t3BeV4xyMI0xg2txkV3uOWNawlXjun+WftzBOpgcgOMPy09fdl+hLZPqR5yBYU3ZMijV0X9Qmm8+wi7pRhGiuCHvK840nlJzQePdoVN2ZlXvldZc0xbFey7HQ=
Date: 1 Feb 2010 14:59:03 -0000
Message-ID: <20100201145903.30670.qmail@simone.iecc.com>
From: John Levine <johnl@taugh.com>
To: asrg@irtf.org
In-Reply-To: <DCF5EE6B7BEBF99354DFB80D@lewes.staff.uscs.susx.ac.uk>
Organization:
Cc:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7bit
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 14:58:31 -0000

>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.

R's,
John