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

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

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G93SL-0007Tm-2x for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 13:27:29 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G93SJ-0005nl-MZ for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 13:27:29 -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 k74HQSNN022673; Fri, 4 Aug 2006 10:26:28 -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 k74HQEMM022641 for <ietf-dkim@mipassoc.org>; Fri, 4 Aug 2006 10:26:15 -0700
Received: (qmail 22447 invoked from network); 4 Aug 2006 17:25:48 -0000
Received: from simone.iecc.com (208.31.42.47) by mail2.iecc.com with QMQP; 4 Aug 2006 17:25:48 -0000
Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 4 Aug 2006 17:25:48 -0000
Date: Fri, 04 Aug 2006 13:25:48 -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: <44D37376.4020408@mtcc.com>
Message-ID: <20060804132203.Y49810@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> <20060804112731.I21459@simone.iecc.com> <44D36B4A.2050903@mtcc.com> <20060804114527.Y27352@simone.iecc.com> <44D37376.4020408@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: 9466e0365fc95844abaf7c3f15a05c7d

>> If SSP says "I sign everything" I have trouble figuring a use for it 
>> other than a flat reject of unsigned messages or at least 4.9 points in 
>> a five point scoring spam filter.

> That's the problem: if you do that, domains like Cisco -- or anybody else
> who uses mailing lists -- will *never* publish a "we sign everything" policy
> even though we do.

And that's a problem because ... ?  There are all sorts of true statements 
that you can make about your outgoing mail, almost none of which are of 
any use to anyone else.  This appears to be one of them.

> 0: "mail from this domain may transit manglers, adjust accordingly"

That's not a bit, that's a fact of life.  None of us have any idea what 
paths our mail might take on its way through the mail morass.

> 1: "the signature should always be intact"

That's someone people could use operationally -- a suggestion to discard 
unsigned mail from you.

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