IETF Logo Mail Archive

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

Michael Thomas <mike@mtcc.com> Sat, 05 August 2006 00:29 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G9A2L-0003QQ-PY for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 20:29:05 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G9A2J-0006VG-Cm for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 20:29:05 -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 k750Rki7013900; Fri, 4 Aug 2006 17:27:46 -0700
Received: from fasolt.mtcc.com (adsl-216-102-208-10.dsl.snfc21.pacbell.net [216.102.208.10]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k750RYQp013874 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-dkim@mipassoc.org>; Fri, 4 Aug 2006 17:27:34 -0700
DKIM-Signature: v=0.4; a=rsa-sha256; q=dns/txt; l=999; t=1154737617; x=115 5601617; c=relaxed/simple; s=dicks.drop.kirkwood; h=Content-Type:From:Subje ct:Content-Transfer-Encoding:MIME-Version; d=mtcc.com; i=mike@mtcc.com; z=F rom:=20Michael=20Thomas=20<mike@mtcc.com>|Subject:=20Re=3A=20[ietf-dkim]=20 A=20more=20fundamental=20SSP=20axiom|Sender:=20|To:=20=20arvel.hathcock@alt n.com|Cc:=20=22'ietf-dkim@mipassoc.org'=22=20<ietf-dkim@mipassoc.org>|Conte nt-Transfer-Encoding:=207bit|MIME-Version:=201.0|Content-Type:=20text/plain =3B=20charset=3DISO-8859-1=3B=20format=3Dflowe d; bh=zyzEEE0g8lbhhg4OH86iJPO/xC/Y+8IAovvgucQWkyY=; b=junrgRlGqaCamGm4n0UsNv/FqqsF4KI8EY3qToP4Z1gu9eBZ/U0cXf0V1I0kc5Cn2AeT3bkM 76eX9xS2oKNudJm+aoEB+/H14wFoE0IjDinFnMRm7LGOFm5QuO1PP/eF;
DKIM-Signature: a=rsa-sha1; q=dns; l=999; t=1154737617; x=1155601617; c=re laxed/simple; s=dicks.drop.kirkwood; h=Content-Type:From:Subject:Content-Tr ansfer-Encoding:MIME-Version; d=mtcc.com; i=mike@mtcc.com; z=From:Michael=2 0Thomas=20<mike@mtcc.com>|Subject:Re=3A=20[ietf-dkim]=20A=20more=20fundamen tal=20SSP=20axiom|Sender:|To:=20arvel.hathcock@altn.com|Cc:=22'ietf-dkim@mi passoc.org'=22=20<ietf-dkim@mipassoc.org>|Content-Transfer-Encoding:7bit|MI ME-Version:1.0|Content-Type:text/plain=3B=20charset=3DISO-8859-1=3B=20forma t=3Dflowe d; X=v=3Dcisco.com=3B=20h=3DTHgzsy76Cqx29/einu/PnNiEwmM=3D; b=Wq/jm6wFkpFcw/mK9i5a2XhYLpQtz1oJ8xkzwYk24cQcYsLOmgOiYxtwIunpXY5tBAhAcCo4 j92nmOHj9Jh4ZlswDWOjAglcUpZ4nOGsvR7ARYT3yVD9jNPTpKnizX/F;
Received: from [192.168.0.102] (sj-natpool-220.cisco.com [128.107.248.220]) (authenticated bits=0) by fasolt.mtcc.com (8.13.6/8.13.1) with ESMTP id k750Qt5D018391 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Aug 2006 17:26:56 -0700
Message-ID: <44D3E5C9.5050408@mtcc.com>
Date: Fri, 04 Aug 2006 17:26:49 -0700
From: Michael Thomas <mike@mtcc.com>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; rv:1.7.3) Gecko/20040913 Thunderbird/0.8 Mnenhy/0.7.2.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: arvel.hathcock@altn.com
Subject: Re: [ietf-dkim] A more fundamental SSP axiom
References: <MDAEMON-F200608041905.AA0542108md50000023415@altn.com>
In-Reply-To: <MDAEMON-F200608041905.AA0542108md50000023415@altn.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Authentication-Results: fasolt.mtcc.com; header.From=mike@mtcc.com; dkim=pass ( sig from mtcc.com/dicks.drop.kirkwood verified; ); header.From=mike@mtcc.com; dkim=pass ( sig from mtcc.com/dicks.drop.kirkwood verified; );
X-XIPE-SCORES: dispose=pass; ACD=1.00; CLAM=0.00; COMPLY=0.00; URL=0.00; SA=0.00; HONEY=0.00;
X-Songbird: Clean, Clean
Cc: "'ietf-dkim@mipassoc.org'" <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.2 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5

Arvel Hathcock wrote:

>>If a signer wants to take that risk, isn't that for them to decide?
>>    
>>
>
>Precisely.
>
>  
>
>>Also, if the usual strategy of a verifier is to bounce (or be
>>encouraged to bounce) the offending email, a "I sign all" sender will
>>almost always know about delivery failures of originally signed
>>traffic and be able to act accordingly. 
>>    
>>

So if I set a policy of "I sign all", and a mailing list mangles it, 
what exactly
is the mailing list receiving the bounce going to do? Blackhole it? Bounce
the user off the list? Anything useful whatsoever?

>
>Right.  I don't see a big reason to worry with this at all.  There are all sorts of reasons SMTP might bounce a message back as it is.
>  
>

That makes the assumption that it gets bounced at all. Lots of things just
silently discard things they don't like these days.  Not that there's 
anything
useful that a mangler is likely to be able to do in any case.

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

v2.23.0 | Report a Bug | By Email