IETF Logo Mail Archive

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

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

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G9A63-0006tY-47 for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 20:32:55 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G9A61-0006vc-OR for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 20:32:55 -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 k750WCAU014412; Fri, 4 Aug 2006 17:32:12 -0700
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.185]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k750W8Ed014376 for <ietf-dkim@mipassoc.org>; Fri, 4 Aug 2006 17:32:08 -0700
Received: by nf-out-0910.google.com with SMTP id g2so610342nfe for <ietf-dkim@mipassoc.org>; Fri, 04 Aug 2006 17:31:42 -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=O6ocrb0cCTeLuksds6uS5cglzCnqvrlGl7Wau3vRuA01jP6tDEyJhYkeW+YyJYPeSjUYZ2cTtquwEc3VEE8ddLdTAGOaLfPOF04bHDpvE/m60qmI/ut1MonUv4YlmIOc1vyHNk5WppkC0Nq5Fy3xU9ONAqxFtmFklhOvqGQeEEc=
Received: by 10.78.170.17 with SMTP id s17mr1627880hue; Fri, 04 Aug 2006 17:31:42 -0700 (PDT)
Received: by 10.78.149.6 with HTTP; Fri, 4 Aug 2006 17:31:42 -0700 (PDT)
Message-ID: <62146370608041731ufd927v8d66be5459ea8982@mail.gmail.com>
Date: Fri, 04 Aug 2006 20:31:42 -0400
From: Damon <deepvoice@gmail.com>
To: arvel.hathcock@altn.com
Subject: Re: [ietf-dkim] A more fundamental SSP axiom
In-Reply-To: <MDAEMON-F200608041910.AA1025596md50000023428@altn.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <MDAEMON-F200608041910.AA1025596md50000023428@altn.com>
X-Songbird: Clean, Clean
Cc: "ietf-dkim@mipassoc.org" <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: 798b2e660f1819ae38035ac1d8d5e3ab

On 8/4/06, Arvel Hathcock <arvel.hathcock@altn.com> wrote:
> > Yes but.. I don't think that everyone is going to be aware of the risk
> > or ignore it thinking it can't happen to them.
>
> Quite the contrary really, I'd think.  And anyway, are we to remove from our work even useful things on the basis that there are some who might not understand it?  Surely not.  We should just do our best to document what we can to help them.
>

Nothing contrary about it... I wish I had a nickle for everyone that
set their SPF records with a ~all. I also think that this would be of
diminishing returns. They may set it up this way.. but the first
problem (or second) they have, it will get turned off. Then what is
their alternative? I don't dislike the idea and if it were released
this way... at least I could say I told you so. I am just hoping we
can come up with a solution that will have a safety or 'Plan B'
attached.


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

v2.23.0 | Report a Bug | By Email