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

Damon <deepvoice@gmail.com> Fri, 04 August 2006 15:54 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G9204-0005bg-5h for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 11:54:12 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G9202-0007NG-QP for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 11:54:12 -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 k74FrVQ9007868; Fri, 4 Aug 2006 08:53:31 -0700
Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.227]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k74FrNpQ007853 for <ietf-dkim@mipassoc.org>; Fri, 4 Aug 2006 08:53:23 -0700
Received: by wr-out-0506.google.com with SMTP id 36so14567wra for <ietf-dkim@mipassoc.org>; Fri, 04 Aug 2006 08:52:58 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=BBy0Rv8W4tV5y37CBMP40C9W0vxrEnCUDz0TbrsqkV03oHFJ5M11jGogWanxwDND7w1txOrlcDOoWJG++F2ZmL9VKPCsAx1mmfmF0rnA2bkjitPGrDrhLiT4ELSeShi/6pEDP28m4A+liSxm52vACUX8j29lSh32RSQnfkxFWQc=
Received: by 10.78.177.3 with SMTP id z3mr1607747hue; Fri, 04 Aug 2006 08:52:57 -0700 (PDT)
Received: by 10.78.149.6 with HTTP; Fri, 4 Aug 2006 08:52:57 -0700 (PDT)
Message-ID: <62146370608040852s20d67351s3374f5bc4c8af6c3@mail.gmail.com>
Date: Fri, 04 Aug 2006 11:52:57 -0400
From: Damon <deepvoice@gmail.com>
To: John L <johnl@iecc.com>
Subject: Re: [ietf-dkim] A more fundamental SSP axiom
In-Reply-To: <20060804112731.I21459@simone.iecc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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> <20060804112731.I21459@simone.iecc.com>
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.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370

On 8/4/06, John L <johnl@iecc.com> wrote:
> > 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.
>

+1
_______________________________________________
NOTE WELL: This list operates according to 
http://mipassoc.org/dkim/ietf-list-rules.html