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

<Bill.Oxley@cox.com> Sat, 05 August 2006 05:05 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G9EM5-0007We-Ro for ietf-dkim-archive@lists.ietf.org; Sat, 05 Aug 2006 01:05:46 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G9EM4-0006yg-Eh for ietf-dkim-archive@lists.ietf.org; Sat, 05 Aug 2006 01:05:45 -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 k7554MTw011657; Fri, 4 Aug 2006 22:04:22 -0700
Received: from cox.com (post4.cox.com [24.248.72.37]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k75548Ow011622 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-dkim@mipassoc.org>; Fri, 4 Aug 2006 22:04:09 -0700
Received: from ([192.168.72.254]) by post4.cox.com with ESMTP id KP-VXH63.206533908; Sat, 05 Aug 2006 01:03:33 -0400
Received: from CATL0MS21.CORP.COX.COM ([10.64.210.21]) by catl0ms23.CORP.COX.COM with Microsoft SMTPSVC(6.0.3790.2668); Sat, 5 Aug 2006 01:03:33 -0400
Received: from CATL0MS02.corp.cox.com ([10.62.210.88]) by CATL0MS21.CORP.COX.COM with Microsoft SMTPSVC(6.0.3790.1830); Sat, 5 Aug 2006 01:03:32 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: RE: [ietf-dkim] A more fundamental SSP axiom
Date: Sat, 05 Aug 2006 01:03:32 -0400
Message-ID: <BB621D48443A854A89D86528F915864C0215F773@CATL0MS02.corp.cox.com>
In-Reply-To: <20060805044640.74696.qmail@snake.corp.yahoo.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [ietf-dkim] A more fundamental SSP axiom
Thread-Index: Aca4StC50VgUWbeiRayukITbxKeirwAAN+4w
From: Bill.Oxley@cox.com
To: MarkD+dkim@yahoo-inc.com, ietf-dkim@mipassoc.org
X-OriginalArrivalTime: 05 Aug 2006 05:03:32.0976 (UTC) FILETIME=[7FEAD700:01C6B84C]
X-Songbird: Clean, Clean
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sb7.songbird.com id k75548Ow011622
Cc:
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: 3e15cc4fdc61d7bce84032741d11c8e5

Perhaps we should work backwards, what are the mechanisms for DKIM
compliant mailing lists?
If a signed message arrives and SSP says 3rd party allowed, evaluate
resign send
If evaluate fails bounce without propagation
If no sig and policy says "I sign all" bounce message
If SSP states "I only sign" forward without adding list signature or
bounce message
Myriad other possibilities
 
Bill Oxley 
Messaging Engineer 
Cox Communications, Inc. 
Alpharetta GA 
404-847-6397 
bill.oxley@cox.com 


-----Original Message-----
From: ietf-dkim-bounces@mipassoc.org
[mailto:ietf-dkim-bounces@mipassoc.org] On Behalf Of Mark Delany
Sent: Saturday, August 05, 2006 12:47 AM
To: ietf-dkim@mipassoc.org
Subject: Re: [ietf-dkim] A more fundamental SSP axiom

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

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