Re: [ietf-dkim] A more fundamental SSP axiom

John L <johnl@iecc.com> Fri, 04 August 2006 15:36 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G91iy-00082V-8e for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 11:36:32 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G91iv-0006RG-S8 for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 11:36:32 -0400
Received: from sb7.songbird.com (sb7.songbird.com [127.0.0.1]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k74FZVSK004682; Fri, 4 Aug 2006 08:35:32 -0700
Received: from xuxa.iecc.com (xuxa.iecc.com [208.31.42.42]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with SMTP id k74FZOrP004616 for <ietf-dkim@mipassoc.org>; Fri, 4 Aug 2006 08:35:24 -0700
Received: (qmail 1216 invoked from network); 4 Aug 2006 15:34:58 -0000
Received: from simone.iecc.com (208.31.42.47) by mail2.iecc.com with QMQP; 4 Aug 2006 15:34:58 -0000
Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 4 Aug 2006 15:34:58 -0000
Date: Fri, 04 Aug 2006 11:34:58 -0400
From: John L <johnl@iecc.com>
To: Michael Thomas <mike@mtcc.com>
Subject: Re: [ietf-dkim] A more fundamental SSP axiom
In-Reply-To: <44D36203.2060803@mtcc.com>
Message-ID: <20060804112731.I21459@simone.iecc.com>
References: <20060802002353.U59653@simone.iecc.com> <44D0E259.7040400@mtcc.com> <20060802165510.X1168@simone.iecc.com> <44D160BD.7080209@mtcc.com> <20060802223619.E86316@simone.iecc.com> <44D24A20.6050109@mtcc.com> <20060803153457.X33570@simone.iecc.com> <44D36203.2060803@mtcc.com>
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Songbird: Clean, Clean
Cc: DKIM List <ietf-dkim@mipassoc.org>
X-BeenThere: ietf-dkim@mipassoc.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF DKIM Discussion List <ietf-dkim.mipassoc.org>
List-Unsubscribe: <http://mipassoc.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=unsubscribe>
List-Archive: <http://mipassoc.org/pipermail/ietf-dkim>
List-Post: <mailto:ietf-dkim@mipassoc.org>
List-Help: <mailto:ietf-dkim-request@mipassoc.org?subject=help>
List-Subscribe: <http://mipassoc.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=subscribe>
Sender: ietf-dkim-bounces@mipassoc.org
Errors-To: ietf-dkim-bounces@mipassoc.org
X-SongbirdInformation: support@songbird.com for more information
X-Songbird-From: ietf-dkim-bounces@mipassoc.org
X-Spam-Score: -0.1 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f

> Part of the problem here is the past record of SPF with over-zealous 550 if
> there's any hint of bogosity. We, for example, would be forced to take down
> a "we sign everything" policy if that were to happen with DKIM -- even though
> we'll be signing everything pretty soon. If there were a qualifier in the "I 
> sign everything policy" that specifically implies that sending a 550 based on a 
> missing DKIM signature alone is extremely bone-headed" then maybe we can both.

I don't see the point.  That last suggestion is, to the recipient, the 
equivalent of a useless "I sign some mail" since you're telling the 
recipient it's OK to accept some amount of both signed and unsigned mail.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Information Superhighwayman wanna-be, http://johnlevine.com, Mayor
"I dropped the toothpaste", said Tom, crestfallenly.
_______________________________________________
NOTE WELL: This list operates according to 
http://mipassoc.org/dkim/ietf-list-rules.html