Re: [Asrg] Adding a spam button to MUAs

"Chris Lewis" <clewis@nortel.com> Fri, 05 February 2010 18:36 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 C2F6D28C147 for <asrg@core3.amsl.com>; Fri, 5 Feb 2010 10:36:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.426
X-Spam-Level:
X-Spam-Status: No, score=-6.426 tagged_above=-999 required=5 tests=[AWL=0.017, 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 4lpxCWm6Kjdf for <asrg@core3.amsl.com>; Fri, 5 Feb 2010 10:36:25 -0800 (PST)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 91B173A6D99 for <asrg@irtf.org>; Fri, 5 Feb 2010 10:36:25 -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 o15IbCl07640 for <asrg@irtf.org>; Fri, 5 Feb 2010 18:37:12 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 13:36:56 -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 13:36:56 -0500
Message-ID: <4B6C653C.7060807@nortel.com>
Date: Fri, 5 Feb 2010 13:36:44 -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>
In-Reply-To: <Pine.GSO.4.64.1002051011310.28969@nber6.nber.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 05 Feb 2010 18:36:56.0999 (UTC) FILETIME=[3221C370:01CAA692]
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 18:36:26 -0000

Daniel Feenberg wrote:
> 
> On Fri, 5 Feb 2010, John Levine wrote:
> 
>>> I haven't been following this thread very closely, but why not just
>>> establish a standard role account on the MUAs designated POP or IMAP
>>> server? Such as arf@pop.example.com? It effectively "preconfigures" the
>>> MUA since "arf" is standard and "example.com" is already known to the MUA.
>>> The less configuration the better, I think.
>> Sorry, wouldn't work.  The name of the POP or IMAP server need not
>> bear any relationship to any email address.  For example, on my
>> system, the server is named imap.iecc.com (yes, even for POP, it
>> deters the clueless) but there are not imap.iecc.com addresses at all.
> 
> I don't understand why this is relevant. If the MTA operator doesn't want 
> to support this feature, he doesn't have to. But if he does wish to 
> support the feature he needs to supply an MX record or accept mail on the 
> POP or IMAP server. Is that such a great burden? Compared to the other 
> suggestions here?

Yes.  Why tie the ARF path to the mailboxes by naming convention?  Don't 
need to.

Use arf@arf.domain.com.  If they're the same machine, fine, make 
arf.domain.com alias to imap.domain.com.  If they're not, you don't have 
to rename your mail infrastructure or screw around with forwarding on 
the imap machine that you may have no control over.