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

"william(at)elan.net" <william@elan.net> Sat, 05 August 2006 00:30 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G9A3F-0004Jy-UA for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 20:30:01 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G9A3E-0006hV-Hx for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 20:30:01 -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 k750T9mp014118; Fri, 4 Aug 2006 17:29:09 -0700
Received: from sokol.elan.net (sokol.elan.net [216.151.192.200]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k750T0E1014094 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-dkim@mipassoc.org>; Fri, 4 Aug 2006 17:29:01 -0700
Received: from sokol.elan.net (sokol [127.0.0.1]) by sokol.elan.net (8.13.1/8.13.1) with ESMTP id k750SUgA005084; Fri, 4 Aug 2006 17:28:31 -0700
Received: from localhost (william@localhost) by sokol.elan.net (8.13.1/8.13.1/Submit) with ESMTP id k750SU62005081; Fri, 4 Aug 2006 17:28:30 -0700
X-Authentication-Warning: sokol.elan.net: william owned process doing -bs
Date: Fri, 04 Aug 2006 17:28:30 -0700
From: "william(at)elan.net" <william@elan.net>
To: Damon <deepvoice@gmail.com>
Subject: Re: [ietf-dkim] A more fundamental SSP axiom
In-Reply-To: <62146370608041645vb82e2faid76479eadfee41c@mail.gmail.com>
Message-ID: <Pine.LNX.4.62.0608041703150.31733@sokol.elan.net>
References: <20060804173538.54245.qmail@simone.iecc.com> <44D3C0BB.9000405@mtcc.com> <20060804174955.N15734@simone.iecc.com> <44D3C8DB.4070101@mtcc.com> <20060804184321.L23892@simone.iecc.com> <20060804231526.71834.qmail@snake.corp.yahoo.com> <62146370608041634t38baf99eu351e0c7373d811d4@mail.gmail.com> <62146370608041645vb82e2faid76479eadfee41c@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Songbird: Clean, Clean
Cc: 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: 21c69d3cfc2dd19218717dbe1d974352

On Fri, 4 Aug 2006, Damon wrote:

> I want to add a little more...
>
> It would also be ok if there was an alternative that was useful... and
> will just refer to my previous posts as to why I thing "I SIGN SOME"'s
> value is not worth the expense.

Before you said you want "I sign some if it comes from this 
server/network". Coming back to this issues, the problem here
is that if signature was actually added and server name is
available you already know it signed it. If the signature is
missing you can't tell it came from that server unless you examine 
Received trace data (unreliable and per RFCs not to be used for
email processing although almost every anti-spam software in
practice violates this now..) or violate RFC2821 session/RFC2822
DATA separation.

Can you think of somethubg else for use in <here> you'd like to
see as part of either
  "I sign all" <here> but may not sign in other cases
  "I sign all" except <here>

Personally cases I see are:
  1. I either sign all myself OR these guys <list domains> sign on
     my behalf
     a. In some special cases it can also be I sign all myself AND
        one of these guys <list domains> will also sign it
  2. I always sign if it comes from[*] <list email address> but
     otherwise I may not add a signature
  3. I always sign when it goes to[*] <list email addresses> but
     otherwise I may not add a signature

[*] From and To are general concepts here and do not necessarilly
     imply "From" and "To" header field specifically

-- 
William Leibzon
Elan Networks
william@elan.net
_______________________________________________
NOTE WELL: This list operates according to 
http://mipassoc.org/dkim/ietf-list-rules.html