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

Mark Delany <MarkD+dkim@yahoo-inc.com> Sat, 05 August 2006 04:48 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G9E4w-0007Fe-IC for ietf-dkim-archive@lists.ietf.org; Sat, 05 Aug 2006 00:48:02 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G9E4u-00024S-5Y for ietf-dkim-archive@lists.ietf.org; Sat, 05 Aug 2006 00:48:02 -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 k754l9G2009700; Fri, 4 Aug 2006 21:47:11 -0700
Received: from snake.corp.yahoo.com (snake.corp.yahoo.com [216.145.52.229]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with SMTP id k754l5Ak009651 for <ietf-dkim@mipassoc.org>; Fri, 4 Aug 2006 21:47:05 -0700
Received: (qmail 74704 invoked by uid 6042); 5 Aug 2006 04:46:40 -0000
Delivered-To: markd-intercept-ietf-dkim@mipassoc.org
DomainKey-Trace: U=http://domainkeys.sourceforge.net; V=$Revision: 1.4 $; h=::::::::::12::::::::::::::::::::::37::::::::1:1::2:1:14:22:1:42:7:11:7:14:6:13:6:6:6:17:2:5:1:5::7:3::2:5::2:::2::::5:::1::4:4:4::1:::::1::1::::24:2:18:8:34:6:5:4:32:1:9:13:23:20:33:9:5:11:15:16:7:2:1:2:7; H=::::::::::12:::12:::::::::::::::::::37::::::::1:1::2:1:14:22:1:42:7:11:7:14:6:13:6:6:6:17:2:5:1:5::7:3::2:5::2:::2::::5:::1::4:4:4::1:::::1::1::::24:2:18:8:34:6:5:4:32:1:9:13:23:20:33:9:5:11:15:16:7:2:1:2:7; b=::::::::::24::::::::::::::::::::::172::14:::::6:::::8:3:8::8:2:1:1:1:1:1:::1:3::::19:5::3:3::1:::::13:1:1:2:3:1:1::::2:1:::3::::::::::53:9:18:16:73:17:19:33:51::2:48:21:40:39:9::25:43:75:20:5:11:1:12:1; B=::::::::::24:::24:::::::::::::::::::172::14:::::6:::::8:3:8::8:2:1:1:1:1:1:::1:3::::19:5::3:3::1:::::13:1:1:2:3:1:1::::2:1:::3::::::::::53:9:18:16:73:17:19:33:51::2:48:21:40:39:9::25:43:75:20:5:11:1:12:1;
DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=snake; d=yahoo-inc.com; b=CzNkhaELIkQZlTsSGWPXh4AzLExDxS3eCWrCv6hbkmPoZzkBPxrJQ4fXx527N153
Received: (qmail 74698 invoked by uid 6042); 5 Aug 2006 04:46:40 -0000
Message-ID: <20060805044640.74696.qmail@snake.corp.yahoo.com>
Date: Sat, 05 Aug 2006 04:46:40 +0000
From: Mark Delany <MarkD+dkim@yahoo-inc.com>
To: ietf-dkim@mipassoc.org
Subject: Re: [ietf-dkim] A more fundamental SSP axiom
Mail-Followup-To: ietf-dkim@mipassoc.org
References: <20060805011337.73202.qmail@snake.corp.yahoo.com> <20060805014139.72093.qmail@simone.iecc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <20060805014139.72093.qmail@simone.iecc.com>
X-Songbird: Clean, Clean
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: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3

On Sat, Aug 05, 2006 at 01:41:39AM -0000, John Levine allegedly wrote:
> >> 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?
> 
> >That's a matter between the "I sign all" and the list. I would say
> >that if it hurts, don't do it.
> 
> No, the sensible user will accept all the mail from the list.  With

Well maybe, but that's not the intent of my style of "I sign all".

If "I sign all" I would much rather no one accept a mail purportedly
from me that doesn't verify. Why would an "I sign all" domain want
mail accepted that can't be proved to be from them?

But them I'm missing this whole "list" issue. It seems to me to be
largely a red-herring because the size of the intersection of "I sign
all" traffic and DKIM-unaware Lists is pure speculation at this stage.


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