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

Damon <deepvoice@gmail.com> Sat, 05 August 2006 00:51 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G9AO1-0000m2-MP for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 20:51:29 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G9AO0-0000ID-7H for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 20:51: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 k750ogRS016359; Fri, 4 Aug 2006 17:50:42 -0700
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k750oK0v016316 for <ietf-dkim@mipassoc.org>; Fri, 4 Aug 2006 17:50:21 -0700
Received: by nf-out-0910.google.com with SMTP id g2so613903nfe for <ietf-dkim@mipassoc.org>; Fri, 04 Aug 2006 17:49:55 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=srH/qk7BhKIkOo+I1++Qxk4J/HDIvvyz4ku6BWzoFH1m4dV5x9BHQj+SoKTuL/oNLss2ANbjp1jjV5QoQoeRGL3MMOxgpIV6ipgfkSawTxqK390VMKsiygrnrN6RI1mWQaN8IJ0NsmxXdrSBYrvWp0SS24gOxYuMMWxxskDo3rI=
Received: by 10.78.127.6 with SMTP id z6mr1773913huc; Fri, 04 Aug 2006 17:49:54 -0700 (PDT)
Received: by 10.78.149.6 with HTTP; Fri, 4 Aug 2006 17:49:54 -0700 (PDT)
Message-ID: <62146370608041749i64b08892q2291f420b4b170e1@mail.gmail.com>
Date: Fri, 04 Aug 2006 20:49:54 -0400
From: Damon <deepvoice@gmail.com>
To: "william(at)elan.net" <william@elan.net>
Subject: Re: [ietf-dkim] A more fundamental SSP axiom
In-Reply-To: <62146370608041733v70bb2954r5b21a8b2ac565ed3@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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> <Pine.LNX.4.62.0608041703150.31733@sokol.elan.net> <62146370608041733v70bb2954r5b21a8b2ac565ed3@mail.gmail.com>
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: e5ba305d0e64821bf3d8bc5d3bb07228

On 8/4/06, Damon <deepvoice@gmail.com> wrote:
> > 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
>

My only question is... where are you going to put all those rules?
I remember having a terrible time with a reverse that went back to
500+ domains my DNS kept timing out before I could get to the bottom
of the list.
Should you or could you put a limit on the number of domains?
And if you did, where would you put the extra?
This is why I went with the CIDR idea when we did SPF. You can have
1000 domains pointing at the same IP all owned by the same guy AND be
legit.
In this case wouldn't it be better to put in an IP?

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