Re: [Asrg] Adding a spam button to MUAs

Daniel Feenberg <feenberg@nber.org> Fri, 05 February 2010 19:55 UTC

Return-Path: <feenberg@nber.org>
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 DCC8E28C1A8 for <asrg@core3.amsl.com>; Fri, 5 Feb 2010 11:55:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.442
X-Spam-Level:
X-Spam-Status: No, score=-6.442 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SUBJECT_FUZZY_TION=0.156, UNPARSEABLE_RELAY=0.001]
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 x3uHHG-GfJRG for <asrg@core3.amsl.com>; Fri, 5 Feb 2010 11:55:34 -0800 (PST)
Received: from mail2.nber.org (mail2.nber.org [66.251.72.79]) by core3.amsl.com (Postfix) with ESMTP id C432C28C177 for <asrg@irtf.org>; Fri, 5 Feb 2010 11:55:34 -0800 (PST)
Received: from nber6.nber.org (nber6.nber.org [66.251.72.76]) by mail2.nber.org (8.14.3/8.13.8) with ESMTP id o15JuGwa029196 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Fri, 5 Feb 2010 14:56:16 -0500 (EST) (envelope-from feenberg@nber.org)
Received: from nber6.nber.org (localhost [127.0.0.1]) by nber6.nber.org (8.13.8+Sun/8.12.10) with ESMTP id o15JsxBF006483; Fri, 5 Feb 2010 14:54:59 -0500 (EST)
Received: from localhost (Unknown UID 1079@localhost) by nber6.nber.org (8.13.8+Sun/8.13.8/Submit) with ESMTP id o15JsxRj006480; Fri, 5 Feb 2010 14:54:59 -0500 (EST)
X-Authentication-Warning: nber6.nber.org: Unknown UID 1079 owned process doing -bs
Date: Fri, 05 Feb 2010 14:54:57 -0500
From: Daniel Feenberg <feenberg@nber.org>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
In-Reply-To: <4B6C653C.7060807@nortel.com>
Message-ID: <Pine.GSO.4.64.1002051453300.5843@nber6.nber.org>
References: <20100205151049.85259.qmail@simone.iecc.com> <Pine.GSO.4.64.1002051011310.28969@nber6.nber.org> <4B6C653C.7060807@nortel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Anti-Virus: Kaspersky Anti-Virus for Linux Mail Server 5.6.39/RELEASE, bases: 20100205 #3428449, check: 20100205 clean
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:55:36 -0000

On Fri, 5 Feb 2010, Chris Lewis wrote:

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

Fine with me. But you really should learn about MX records - they are very 
useful and have been standardized for many years now.

Daniel Feenberg


> _______________________________________________
> Asrg mailing list
> Asrg@irtf.org
> http://www.irtf.org/mailman/listinfo/asrg
>