Re: [Asrg] Adding a spam button to MUAs

"Chris Lewis" <clewis@nortel.com> Fri, 05 February 2010 19:15 UTC

Return-Path: <CLEWIS@nortel.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 1662B3A69F9 for <asrg@core3.amsl.com>; Fri, 5 Feb 2010 11:15:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.433
X-Spam-Level:
X-Spam-Status: No, score=-6.433 tagged_above=-999 required=5 tests=[AWL=0.010, 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 vQnTVISXwZH0 for <asrg@core3.amsl.com>; Fri, 5 Feb 2010 11:14:59 -0800 (PST)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 530D23A69F7 for <asrg@irtf.org>; Fri, 5 Feb 2010 11:14:59 -0800 (PST)
Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id o15JFll20820 for <asrg@irtf.org>; Fri, 5 Feb 2010 19:15:47 GMT
Received: from zrtphx5h0.corp.nortel.com ([47.140.202.65]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 5 Feb 2010 14:15:46 -0500
Received: from [47.130.80.234] (47.130.80.234) by zrtphx5h0.corp.nortel.com (47.140.202.65) with Microsoft SMTP Server (TLS) id 8.1.340.0; Fri, 5 Feb 2010 14:15:46 -0500
Message-ID: <4B6C6E56.5010802@nortel.com>
Date: Fri, 5 Feb 2010 14:15:34 -0500
From: "Chris Lewis" <clewis@nortel.com>
Organization: Nortel
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23) Gecko/20090812 Lightning/0.9 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
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>
In-Reply-To: <F20D7208-2839-4B53-ADC9-471D11880F70@blighty.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 05 Feb 2010 19:15:46.0467 (UTC) FILETIME=[9E9A5F30:01CAA697]
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 19:15:01 -0000

Steve Atkins wrote:

Okay, but "arf" is so short ;-) And we have to get everybody else to use it.

"feedback" works too.

> The only setting that the MUA is likely to have access to is the name of the IMAP or POP3 server. As IMAP and POP3 are not name-based, the entry there could easily be domain.com, mail.domain.com, imap.domain.com or pop.domain.com or smtp.domain.com or even www.domain.com.

It has the default name used in inbound email, as well as (usually) an 
email address used as a userid.  Per delivery server.  It may even be 
able to see the rcpt to (or the MTA could "help".  Oh, never mind).

> One option is to have the MUA "use some heuristic to find the 'domain' associated with that hostname", but past experience with SSP suggests that it makes people point and laugh at you and start mentioning things like imap.aardvark.us.com.
> 
> Another would be to prepend "feedback." to the imap server name - so do an MX lookup for "feedback.imap.domain.com" to discover whether it's to enable the TiS button. That'll either need a DNS record added for every possible name for the IMAP server, or accept that it won't autoconfigure unless the recipient uses the name for the IMAP server you're expecting, either of which seems reasonable.
> 
> (That doing MX lookups is not something that MUAs typically need code for, and that isn't supported by base API, is a minor issue but worth mentioning).

Agreed.  I suspect many MUAs are completely incapable of doing direct to 
MX, and don't do MX lookups.  See other suggestion, where I say "Use 
normal submit mechanism".