Re: [Asrg] Adding a spam button to MUAs

Steve Atkins <steve@blighty.com> Fri, 05 February 2010 20:07 UTC

Return-Path: <steve@blighty.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 B59A13A6DFE for <asrg@core3.amsl.com>; Fri, 5 Feb 2010 12:07:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level:
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=-0.006, 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 2WdwTmqef15D for <asrg@core3.amsl.com>; Fri, 5 Feb 2010 12:07:33 -0800 (PST)
Received: from m.wordtothewise.com (fruitbat.wordtothewise.com [208.187.80.135]) by core3.amsl.com (Postfix) with ESMTP id F10C93A6DF6 for <asrg@irtf.org>; Fri, 5 Feb 2010 12:07:32 -0800 (PST)
Received: from platterhard.wordtothewise.com (184.wordtothewise.com [208.187.80.184]) by m.wordtothewise.com (Postfix) with ESMTP id 984234F8200 for <asrg@irtf.org>; Fri, 5 Feb 2010 12:08:24 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1077)
From: Steve Atkins <steve@blighty.com>
In-Reply-To: <4B6C7925.2090704@nortel.com>
Date: Fri, 5 Feb 2010 12:08:24 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <81225C16-4E39-4F10-A3DC-B15B1398452D@blighty.com>
References: <20100205151049.85259.qmail@simone.iecc.com> <Pine.GSO.4.64.1002051011310.28969@nber6.nber.org> <4B6C653C.7060807@nortel.com> <F20D7208-2839-4B53-ADC9-471D11880F70@blighty.com> <4B6C6E56.5010802@nortel.com> <9B9E89BC-32B9-41D2-B1EA-AA5C78FFBAFE@blighty.com> <4B6C7925.2090704@nortel.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
X-Mailer: Apple Mail (2.1077)
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: Fri, 05 Feb 2010 20:07:33 -0000

On Feb 5, 2010, at 12:01 PM, Chris Lewis wrote:

> Steve Atkins wrote:
> 
>> Of those, the only thing that's actually associated with the inbound mailbox is the incoming mail server.
> 
> As you suggest, key it to "feedback@feedback.<incoming server name>".

Yup.

> 
>>> But a critical bit of UI design is that it should be clear to the user whether something will happen, or not. So for this to be workable the MUA needs to be able to configure itself to show or hide the TiS button (or grey it out, or whatever UI idiom you like).
>> The charm of using an MX record to configure this is that the MUA can do an MX lookup to know whether to show or hide the button. That's pretty clean, and if I were coding an MUA I'd be happy to do it that way, but it's not necessarily a _trivial_ thing to add to a codebase, especially via plugin, so it's worth considering.
> 
> From the perspective of code base, checking for an A record for "feedback.<incoming server name>" would be simpler.  The MTA doesn't need to use DNS to deliver, and you really don't want the MUA to be establishing direct connections anyway.  Fixed route to whereever in the MTA.

So an A record for feedback.imap.example.com to demonstrate existence, and an MX record for the same to actually control delivery.

So the MUA can lookup the A record for feedback.imap.example.com to enable the TiS button, and when the TiS button is pressed it just sends email, using it's normal submission server, to feedback@feedback.imap.example.com or something like that, and the smarthost delivers that just as it would any other email.

If the MUA checks for the A record when fetching mail, rather than when displaying it, it'll all work when I'm on a plane too. Yay for store-and-forward!

Cheers,
  Steve