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

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

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G99y4-0006gS-Qf for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 20:24:40 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G99y1-0005yT-Qx for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 20:24:40 -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 k750KUe9013118; Fri, 4 Aug 2006 17:20:30 -0700
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k750KJFN013074 for <ietf-dkim@mipassoc.org>; Fri, 4 Aug 2006 17:20:20 -0700
Received: by nf-out-0910.google.com with SMTP id g2so607938nfe for <ietf-dkim@mipassoc.org>; Fri, 04 Aug 2006 17:19:54 -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=dgo2p6srxIFxnzlUOtrscp+rrRFgQZ4lOYHLo7IQEuKJcE82AKAj4V/pW9xadfHU2QkMxQwYh7O95JB0wEhklKayOxaB0S2E9GXJxOJnuHY9mLX/do8+kKFb/BiYjhBGqA3Es73lFSZWjPWdUocWSz3r1lx7BVewStm7ox85UdA=
Received: by 10.78.128.11 with SMTP id a11mr1122381hud; Fri, 04 Aug 2006 17:19:54 -0700 (PDT)
Received: by 10.78.149.6 with HTTP; Fri, 4 Aug 2006 17:19:53 -0700 (PDT)
Message-ID: <62146370608041719q60d2c3e6o42e5db4613b759a@mail.gmail.com>
Date: Fri, 04 Aug 2006 20:19:53 -0400
From: Damon <deepvoice@gmail.com>
To: arvel.hathcock@altn.com
Subject: Re: [ietf-dkim] A more fundamental SSP axiom
In-Reply-To: <MDAEMON-F200608041905.AA0542108md50000023415@altn.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <MDAEMON-F200608041905.AA0542108md50000023415@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: 7d33c50f3756db14428398e2bdedd581

> > Also, if the usual strategy of a verifier is to bounce (or be
> > encouraged to bounce) the offending email, a "I sign all" sender will
> > almost always know about delivery failures of originally signed
> > traffic and be able to act accordingly.
>
> Right.  I don't see a big reason to worry with this at all.  There are all sorts of reasons SMTP might bounce a message back as it is.

True, but those bounces are more than likely going back to the user to
let them know, their buddy changed his email address, or they
mistyped, etc. Things that they can effect.
 This bounce will be utterly useless to the user because they can't do
anything about it except to resend. So they get 10 more bounces for 10
re-sends... then what.. my phone starts ringing off the hook. Not
something I will likely be able to fix right away.... and my phone
keeps ringing.

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