IETF Logo Mail Archive

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

Damon <deepvoice@gmail.com> Fri, 04 August 2006 22:11 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G97sq-0000Ro-74 for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 18:11:08 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G97so-0007PW-RK for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 18:11:08 -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 k74M8xSH028827; Fri, 4 Aug 2006 15:08:59 -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 k74M8uKX028813 for <ietf-dkim@mipassoc.org>; Fri, 4 Aug 2006 15:08:56 -0700
Received: by nf-out-0910.google.com with SMTP id y38so171799nfb for <ietf-dkim@mipassoc.org>; Fri, 04 Aug 2006 15:08:30 -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=Uq5KKm/vNyxFHqLKqBSTDMJKP1GSFDhTUsHVvMycpw784HW23CNgvs8+POIV4XfpIsAWEmmWF/h2tVlQYQumg/8VrpA7NPwOb6s25EDZwbOPvwY80JPV4HExPbZIJBkotwxUFHsIabmL1OaHT1lLztbFUdy1giv9vc/GHUqO/SQ=
Received: by 10.78.147.3 with SMTP id u3mr1728249hud; Fri, 04 Aug 2006 15:08:30 -0700 (PDT)
Received: by 10.78.149.6 with HTTP; Fri, 4 Aug 2006 15:08:25 -0700 (PDT)
Message-ID: <62146370608041508m1a4064eeg4bc6732ad1ed94bf@mail.gmail.com>
Date: Fri, 04 Aug 2006 18:08:25 -0400
From: Damon <deepvoice@gmail.com>
To: Hector Santos <hsantos@santronics.com>
Subject: Re: [ietf-dkim] A more fundamental SSP axiom
In-Reply-To: <016201c6b811$0532d4d0$0201a8c0@hdev1>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20060802002353.U59653@simone.iecc.com> <20060804114527.Y27352@simone.iecc.com> <44D37376.4020408@mtcc.com> <20060804132203.Y49810@simone.iecc.com> <EAF17954-74A3-4374-A059-B31A1414B350@mail-abuse.org> <62146370608041122t779d200h1b29a659ac8ad612@mail.gmail.com> <44D3B49D.9090800@mtcc.com> <62146370608041406i74f707ffgf708bafe87784d97@mail.gmail.com> <44D3BB65.20702@mtcc.com> <016201c6b811$0532d4d0$0201a8c0@hdev1>
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.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d

>  4.7.  DSAP Tag: t=y
>
>   The t=y tag is optional.  If defined, the domain is currently testing
>   DKIM.  Verifiers SHOULD NOT treat testers any different from
>   production mode signers.  It SHOULD NOT be used as a way to bypass a
>   failed signature classification policies.  However, verifiers SHOULD
>   track testers for over extended usage of test signatures and MAY
>   consider using the results to provide feedback to the domain.
>
> And other words, the testing flag will not be tolerated as well.
>

Whew Hector,

 I see what you are getting at but... have any idea how many domains I
am currently tracking for reputation?! How long would I have to keep
that data?
The bots would cause me to get google size boxes alone.
Reminds me of the time I suggested a "auto-expiring" DNS tag. That
went over like a lead balloon.

 Is there another way you could do this?


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