Re: [Asrg] We don't need no stinkin IMAP or POP, was Adding a spam button to MUAs

Michael Thomas <mike@mtcc.com> Sun, 07 February 2010 00:37 UTC

Return-Path: <mike@mtcc.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 BEAFC3A6FB0 for <asrg@core3.amsl.com>; Sat, 6 Feb 2010 16:37:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.443
X-Spam-Level:
X-Spam-Status: No, score=-2.443 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 g0t26tZe0jWy for <asrg@core3.amsl.com>; Sat, 6 Feb 2010 16:37:45 -0800 (PST)
Received: from mtcc.com (mtcc.com [64.142.29.208]) by core3.amsl.com (Postfix) with ESMTP id B1F173A6FB1 for <asrg@irtf.org>; Sat, 6 Feb 2010 16:37:45 -0800 (PST)
Received: from piolinux.mtcc.com (206-104-215-159.volcano.net [206.104.215.159] (may be forged)) (authenticated bits=0) by mtcc.com (8.14.3/8.14.3) with ESMTP id o170cbFt010323 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <asrg@irtf.org>; Sat, 6 Feb 2010 16:38:39 -0800
Message-ID: <4B6E0B8B.30500@mtcc.com>
Date: Sat, 06 Feb 2010 16:38:35 -0800
From: Michael Thomas <mike@mtcc.com>
User-Agent: Thunderbird 2.0.0.14 (X11/20080501)
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <20100206062322.5553.qmail@simone.iecc.com> <4B6DBEC2.7010306@mtcc.com> <201002062323.SAA25605@Sparkle.Rodents-Montreal.ORG>
In-Reply-To: <201002062323.SAA25605@Sparkle.Rodents-Montreal.ORG>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=715; t=1265503121; x=1266367121; c=relaxed/simple; s=thundersaddle.kirkwood; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=mtcc.com; i=mike@mtcc.com; z=From:=20Michael=20Thomas=20<mike@mtcc.com> |Subject:=20Re=3A=20[Asrg]=20We=20don't=20need=20no=20stink in=20IMAP=20or=20POP,=20was=20Adding=20a=20spam=0A=20button= 20to=20MUAs |Sender:=20 |To:=20Anti-Spam=20Research=20Group=20-=20IRTF=20<asrg@irtf .org> |Content-Type:=20text/plain=3B=20charset=3DISO-8859-1=3B=20 format=3Dflowed |Content-Transfer-Encoding:=207bit |MIME-Version:=201.0; bh=aoo9EVpz5eGefWFRgkgk6p34kjYUEFcDxXGB6LGWtZE=; b=DbbRH5OprPVTGz7gAJzlELWUq4a4cd+ZylfaJ/gr9f+X78ag6X9Ju0DnSy /xALD6NwqDL2i2zmgXx6EZxd5BkxHwSKfQlKSeIetRPu9LLiJyyZVlq63G5M hovXIUztcp4ER6OtCD/xJHNDHNb0uq++IRgLwplLW1Vv7OYUJEd+s=;
Authentication-Results: ; v=0.1; dkim=pass header.i=mike@mtcc.com ( sig from mtcc.com/thundersaddle.kirkwood verified; ); dkim-asp=pass header.From=mike@mtcc.com
Subject: Re: [Asrg] We don't need no stinkin IMAP or POP, was 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: Sun, 07 Feb 2010 00:37:46 -0000

der Mouse wrote:
>>>> [...TXT...]
>>>>         
>>> [...SRV...]
>>>       
>> I think that the dkim/spf experience is that anything beyond A and
>> CNAME causes some dns providers out there to fail.
>>     
>
> So what?  No matter what we do, it will cause some providers to fail.
> Heck, some of them fail without our doing anything at all.
>
> If anything, this would be a good thing, in that it may lead to such
> bustification getting fixed, much the way DKIM/SPF have (in the
> evolutionary sense) exerted pressure against unsupport for TXT.
>
>   
I'm only reporting what we've seen. SRV is likely to be more problematic
because it's less common, but even TEXT isn't without issue.

Mike