Re: [ietf-dkim] The problem with sender policy
Arvel Hathcock <arvel.hathcock@altn.com> Sun, 06 August 2006 20:28 UTC
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G9pF5-0005XN-M0 for ietf-dkim-archive@lists.ietf.org; Sun, 06 Aug 2006 16:28:59 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G9pF4-0007ku-6o for ietf-dkim-archive@lists.ietf.org; Sun, 06 Aug 2006 16:28:59 -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 k76KRwdc030228; Sun, 6 Aug 2006 13:27:58 -0700
Received: from c3po.altn.com (c3po.altn.com [65.240.66.134]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k76KRj8Z030177 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for <ietf-dkim@mipassoc.org>; Sun, 6 Aug 2006 13:27:46 -0700
DKIM-Signature: a=rsa-sha1; c=simple; d=altn.com; s=c3po; l=1282; x=1155479213; q=dns; h=DomainKey-Signature:Received:Message-ID: Date:From:User-Agent:MIME-Version:To:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding:Reply-To; z=D omainKey-Signature:=20a=3Drsa-sha1=3B=20s=3Dc3po=3B=20d=3Daltn.c om=3B=0D=0A=09c=3Dnofws=3B=20q=3Ddns=3B=20h=3Dmessage-id=3Afrom= 3B=0D=0A=09b=3DhvZFDBMP2M0alixeQS+LBCYFk7vXt11VGbhDISJ/hw52SKlBf H9i/kMf6itL=0D=0A=09MAr2Xrvn1yWbfw3ZfkfKLRruGM4jQJ18oOFt/7tLIJ79 pcA0vnWbiVxu9=0D=0A=092mGxFVQu7lOWi7Y5DpZLeIpuRgi6h+AxiPlop4we6k 3klFE2uShnrU=3D=3B|Received:=20from=20[192.168.1.107]=20by=20alt n.com=0D=0A=09(MDaemon=20PRO=20v9.0.6)=0D=0A=09with=20ESMTP=20id =20md50001713227.msg=0D=0A=09for=20<ietf-dkim@mipassoc.org>=3B=2 0Sun,=2006=20Aug=202006=2015=3A26=3A52=20-0500|Message-ID:=20<44 D65026.4090908@altn.com>|Date:=20Sun,=2006=20Aug=202006=2015=3A2 5=3A10=20-0500|From:=20Arvel=20Hathcock=20<arvel.hathcock@altn.c om>|User-Agent:=20Thunderbird=201.5.0.5=20(Windows/20060719)|MIM E-Version:=201.0|To:=20=20ietf-dkim@mipassoc.org|Subject:=20Re=3 A=20[ietf-dkim]=20The=20problem=20with=20sender=20policy|Referen ces:=20<20060805034058.861.qmail@simone.iecc.com><44D4FB5A.50207 04@mtcc.com>=09<20060805163953.Q47527@simone.iecc.com>=09<015701 c6b8e3$9f7d8c10$0201a8c0@hdev1>=09<Pine.LNX.4.62.0608051701210.1 1690@sokol.elan.net>=20<20060805204554.R185@simone.iecc.com>|In- Reply-To:=20<20060805204554.R185@simone.iecc.com>|Content-Type:= 20text/plain=3B=20charset=3DISO-8859-1=3B=20format=3Dflowed|Cont ent-Transfer-Encoding:=207bit|Reply-To:=20arvel.hathcock@altn.co m; b=TqEmrmAbXhOTB2KUinxVIqVx2zBlQthGM/uqIhWDSqWxQZgF+eSAaDjL0uJ gFwLxtiXXLWn6xOU5KM7P4s+dK6FF2vjJbp3geR+xOXhswR2WQ0xC/HCu3ppUy4p hTvDOP7JrWxu+K040G1WjHzCXbue8GdjbdK0rCDj//fj3rcI=
DKIM-Signature: v=0.4; a=rsa-sha256; c=simple; d=altn.com; s=c3po; l=1282; x=1155479213; q=dns; h=DomainKey-Signature: Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding: Reply-To; z=DomainKey-Signature:=20a=3Drsa-sha1=3B=20s=3Dc3po=3B =20d=3Daltn.com=3B=0D=0A=09c=3Dnofws=3B=20q=3Ddns=3B=20h=3Dmessa ge-id=3Afrom=3B=0D=0A=09b=3DhvZFDBMP2M0alixeQS+LBCYFk7vXt11VGbhD ISJ/hw52SKlBfH9i/kMf6itL=0D=0A=09MAr2Xrvn1yWbfw3ZfkfKLRruGM4jQJ1 8oOFt/7tLIJ79pcA0vnWbiVxu9=0D=0A=092mGxFVQu7lOWi7Y5DpZLeIpuRgi6h +AxiPlop4we6k3klFE2uShnrU=3D=3B|Received:=20from=20[192.168.1.10 7]=20by=20altn.com=0D=0A=09(MDaemon=20PRO=20v9.0.6)=0D=0A=09with =20ESMTP=20id=20md50001713227.msg=0D=0A=09for=20<ietf-dkim@mipas soc.org>=3B=20Sun,=2006=20Aug=202006=2015=3A26=3A52=20-0500|Mess age-ID:=20<44D65026.4090908@altn.com>|Date:=20Sun,=2006=20Aug=20 2006=2015=3A25=3A10=20-0500|From:=20Arvel=20Hathcock=20<arvel.ha thcock@altn.com>|User-Agent:=20Thunderbird=201.5.0.5=20(Windows/ 20060719)|MIME-Version:=201.0|To:=20=20ietf-dkim@mipassoc.org|Su bject:=20Re=3A=20[ietf-dkim]=20The=20problem=20with=20sender=20p olicy|References:=20<20060805034058.861.qmail@simone.iecc.com><4 4D4FB5A.5020704@mtcc.com>=09<20060805163953.Q47527@simone.iecc.c om>=09<015701c6b8e3$9f7d8c10$0201a8c0@hdev1>=09<Pine.LNX.4.62.06 08051701210.11690@sokol.elan.net>=20<20060805204554.R185@simone. iecc.com>|In-Reply-To:=20<20060805204554.R185@simone.iecc.com>|C ontent-Type:=20text/plain=3B=20charset=3DISO-8859-1=3B=20format= 3Dflowed|Content-Transfer-Encoding:=207bit|Reply-To:=20arvel.hat hcock@altn.com; bh=wqvAZKe5pS/TKsQoPUjL20VR/YEalBfm6BMQcWo+3sY=; b=mHGypA8QjuOmTeprBof+rWCnAlCLJSJGEz6XIa/6cYKKJv9uihSH6JpbCp95or TIsfhMXsJt+SO7SE4lwyKs+QeHuAg/dG1zouH3+wQODhukU8SsgjROAiGI/QuIWg Upp7naXFlchIswiL9ge/Ep0bG4H/Fr6WuylnZgEqOn0MU=
DomainKey-Signature: a=rsa-sha1; s=c3po; d=altn.com; c=nofws; q=dns; h=message-id:from; b=hvZFDBMP2M0alixeQS+LBCYFk7vXt11VGbhDISJ/hw52SKlBfH9i/kMf6itL MAr2Xrvn1yWbfw3ZfkfKLRruGM4jQJ18oOFt/7tLIJ79pcA0vnWbiVxu9 2mGxFVQu7lOWi7Y5DpZLeIpuRgi6h+AxiPlop4we6k3klFE2uShnrU=;
Received: from [192.168.1.107] by altn.com (MDaemon PRO v9.0.6) with ESMTP id md50001713227.msg for <ietf-dkim@mipassoc.org>; Sun, 06 Aug 2006 15:26:52 -0500
Message-ID: <44D65026.4090908@altn.com>
Date: Sun, 06 Aug 2006 15:25:10 -0500
From: Arvel Hathcock <arvel.hathcock@altn.com>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: ietf-dkim@mipassoc.org
Subject: Re: [ietf-dkim] The problem with sender policy
References: <20060805034058.861.qmail@simone.iecc.com><44D4FB5A.5020704@mtcc.com> <20060805163953.Q47527@simone.iecc.com> <015701c6b8e3$9f7d8c10$0201a8c0@hdev1> <Pine.LNX.4.62.0608051701210.11690@sokol.elan.net> <20060805204554.R185@simone.iecc.com>
In-Reply-To: <20060805204554.R185@simone.iecc.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Authenticated-Sender: Arvel.Hathcock@altn.com
X-HashCash: 1:21:060806:md50001713227::rDWeDSF4ao3jYxxW:00008EfK
X-Spam-Processed: c3po.altn.com, Sun, 06 Aug 2006 15:26:52 -0500 (not processed: message from trusted or authenticated source)
X-MDRemoteIP: 24.0.47.1
X-Return-Path: arvel.hathcock@altn.com
X-Envelope-From: arvel.hathcock@altn.com
X-MDaemon-Deliver-To: ietf-dkim@mipassoc.org
X-MDAV-Processed: c3po.altn.com, Sun, 06 Aug 2006 15:26:53 -0500
X-Songbird: Clean, Clean
X-BeenThere: ietf-dkim@mipassoc.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: arvel.hathcock@altn.com
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
> It's true, I don't, and I've been trying to figure out why not. It > finally came to me: senders are not the right people to judge their > own importance. In my view, SSP is not a "judgement of one's own importance". It's simply an advertisement to others through which some assessment of authenticity might be usefully gleaned and potentially used. I see nothing self-absorbed or arrogant in providing that advertisement. To the contrary, I see it as useful to the email community at large. > When I think of SSP records saying dump mail if it's not signed, I see > a bunch of tiny gorillas*, beating their teensy chests and saying in > high squeaky voices, "Beware, oh Internet, of the Scourge of Criminals > attempting to forge the image of my Inestimable Personage, and do not > DARE to be fooled by these Base Mockeries of Communication!" First, SSP doesn't say "dump mail if it's not signed" -- that might be an outcome but that's up to the receiver and needn't be an SSP mandate. Second, if one ignores the irrelevance of words like "teensy" and "high squeaky voices" etc it becomes apparent that every gorilla (regardless of size) has the right (and duty) to protect his domain from abuse as far as possible. -- Arvel _______________________________________________ NOTE WELL: This list operates according to http://mipassoc.org/dkim/ietf-list-rules.html
- Re: [ietf-dkim] A more fundamental SSP axiom Paul Hoffman
- [ietf-dkim] A more fundamental SSP axiom John L
- Re: [ietf-dkim] A more fundamental SSP axiom Dave Crocker
- Re: [ietf-dkim] A more fundamental SSP axiom wayne
- Re: [ietf-dkim] A more fundamental SSP axiom Scott Kitterman
- Re: [ietf-dkim] A more fundamental SSP axiom Dave Crocker
- Re: [ietf-dkim] A more fundamental SSP axiom Michael Thomas
- RE: [ietf-dkim] A more fundamental SSP axiom Arvel Hathcock
- Re: [ietf-dkim] A more fundamental SSP axiom Dave Crocker
- RE: [ietf-dkim] A more fundamental SSP axiom Bill.Oxley
- Re: [ietf-dkim] A more fundamental SSP axiom Dave Crocker
- RE: [ietf-dkim] A more fundamental SSP axiom Arvel Hathcock
- Re: [ietf-dkim] A more fundamental SSP axiom Douglas Otis
- RE: [ietf-dkim] A more fundamental SSP axiom Arvel Hathcock
- Re: [ietf-dkim] A more fundamental SSP axiom Hector Santos
- Re: [ietf-dkim] A more fundamental SSP axiom Arvel Hathcock
- Re: [ietf-dkim] A more fundamental SSP axiom Damon
- RE: [ietf-dkim] A more fundamental SSP axiom Paul Hoffman
- Re: [ietf-dkim] A more fundamental SSP axiom Michael Thomas
- Re: [ietf-dkim] A more fundamental SSP axiom John L
- RE: [ietf-dkim] A more fundamental SSP axiom Bill.Oxley
- Re: [ietf-dkim] A more fundamental SSP axiom Dave Crocker
- Re: [ietf-dkim] A more fundamental SSP axiom John L
- Re: [ietf-dkim] A more fundamental SSP axiom Douglas Otis
- Re: [ietf-dkim] A more fundamental SSP axiom Michael Thomas
- Re: [ietf-dkim] A more fundamental SSP axiom John L
- Re: [ietf-dkim] A more fundamental SSP axiom Douglas Otis
- Re: [ietf-dkim] A more fundamental SSP axiom Hector Santos
- Re: [ietf-dkim] A more fundamental SSP axiom Michael Thomas
- Re: [ietf-dkim] A more fundamental SSP axiom John L
- Re: [ietf-dkim] A more fundamental SSP axiom Michael Thomas
- Re: [ietf-dkim] A more fundamental SSP axiom Damon
- Re: [ietf-dkim] A more fundamental SSP axiom John L
- Re: [ietf-dkim] A more fundamental SSP axiom Michael Thomas
- Re: [ietf-dkim] A more fundamental SSP axiom Stephen Farrell
- Re: [ietf-dkim] A more fundamental SSP axiom Dave Crocker
- Re: [ietf-dkim] A more fundamental SSP axiom Douglas Otis
- Re: [ietf-dkim] A more fundamental SSP axiom Michael Thomas
- Re: [ietf-dkim] A more fundamental SSP axiom Steve Atkins
- Re: [ietf-dkim] A more fundamental SSP axiom Damon
- Re: [ietf-dkim] A more fundamental SSP axiom Michael Thomas
- Re: [ietf-dkim] A more fundamental SSP axiom Damon
- Re: [ietf-dkim] A more fundamental SSP axiom Michael Thomas
- Re: [ietf-dkim] A more fundamental SSP axiom Michael Thomas
- Re: [ietf-dkim] A more fundamental SSP axiom Steve Atkins
- Re: [ietf-dkim] A more fundamental SSP axiom Michael Thomas
- Re: [ietf-dkim] A more fundamental SSP axiom Hector Santos
- Re: [ietf-dkim] A more fundamental SSP axiom John L
- Re: [ietf-dkim] A more fundamental SSP axiom Damon
- Re: [ietf-dkim] A more fundamental SSP axiom John L
- Re: [ietf-dkim] A more fundamental SSP axiom John Levine
- Re: [ietf-dkim] A more fundamental SSP axiom Douglas Otis
- Re: [ietf-dkim] A more fundamental SSP axiom John L
- [ietf-dkim] SSP thought experiment John L
- Re: [ietf-dkim] A more fundamental SSP axiom Douglas Otis
- Re: [ietf-dkim] A more fundamental SSP axiom Damon
- Re: [ietf-dkim] A more fundamental SSP axiom Damon
- Re: [ietf-dkim] SSP thought experiment Douglas Otis
- Re: [ietf-dkim] A more fundamental SSP axiom Damon
- Re: [ietf-dkim] A more fundamental SSP axiom Damon
- RE: [ietf-dkim] SSP thought experiment Bill.Oxley
- RE: [ietf-dkim] SSP thought experiment John L
- RE: [ietf-dkim] A more fundamental SSP axiom Hallam-Baker, Phillip
- RE: [ietf-dkim] A more fundamental SSP axiom John L
- RE: [ietf-dkim] A more fundamental SSP axiom Hallam-Baker, Phillip
- Re: [ietf-dkim] A more fundamental SSP axiom Dave Crocker
- Re: [ietf-dkim] A more fundamental SSP axiom Dave Crocker
- Re: [ietf-dkim] A more fundamental SSP axiom wayne
- Re: [ietf-dkim] A more fundamental SSP axiom Michael Thomas
- Re: [ietf-dkim] A more fundamental SSP axiom Damon
- Re: [ietf-dkim] A more fundamental SSP axiom Hector Santos
- Re: [ietf-dkim] A more fundamental SSP axiom Michael Thomas
- Re: [ietf-dkim] A more fundamental SSP axiom Hector Santos
- Re: [ietf-dkim] A more fundamental SSP axiom Michael Thomas
- Re: [ietf-dkim] A more fundamental SSP axiom Michael Thomas
- Re: [ietf-dkim] A more fundamental SSP axiom Damon
- Re: [ietf-dkim] A more fundamental SSP axiom Hector Santos
- Re: [ietf-dkim] A more fundamental SSP axiom Damon
- Re: [ietf-dkim] A more fundamental SSP axiom Damon
- Re: [ietf-dkim] A more fundamental SSP axiom John L
- Re: [ietf-dkim] A more fundamental SSP axiom william(at)elan.net
- Re: [ietf-dkim] A more fundamental SSP axiom Michael Thomas
- RE: [ietf-dkim] A more fundamental SSP axiom Bill.Oxley
- Re: [ietf-dkim] A more fundamental SSP axiom Hector Santos
- Re: [ietf-dkim] A more fundamental SSP axiom Damon
- Re: [ietf-dkim] A more fundamental SSP axiom John L
- Re: [ietf-dkim] A more fundamental SSP axiom Michael Thomas
- Re: [ietf-dkim] A more fundamental SSP axiom Michael Thomas
- Re: [ietf-dkim] A more fundamental SSP axiom Dave Crocker
- Re: [ietf-dkim] A more fundamental SSP axiom Mark Delany
- Re: [ietf-dkim] A more fundamental SSP axiom Damon
- Re: [ietf-dkim] A more fundamental SSP axiom Damon
- RE: [ietf-dkim] A more fundamental SSP axiom Arvel Hathcock
- RE: [ietf-dkim] A more fundamental SSP axiom Arvel Hathcock
- Re: [ietf-dkim] A more fundamental SSP axiom Damon
- Re: [ietf-dkim] A more fundamental SSP axiom Michael Thomas
- Re: [ietf-dkim] A more fundamental SSP axiom william(at)elan.net
- Re: [ietf-dkim] A more fundamental SSP axiom Damon
- Re: [ietf-dkim] A more fundamental SSP axiom Damon
- Re: [ietf-dkim] A more fundamental SSP axiom Damon
- Re: [ietf-dkim] A more fundamental SSP axiom Mark Delany
- Re: [ietf-dkim] A more fundamental SSP axiom Douglas Otis
- Re: [ietf-dkim] A more fundamental SSP axiom Hector Santos
- Re: [ietf-dkim] A more fundamental SSP axiom Michael Thomas
- Re: [ietf-dkim] A more fundamental SSP axiom Damon
- RE: [ietf-dkim] A more fundamental SSP axiom Bill.Oxley
- Re: [ietf-dkim] A more fundamental SSP axiom Mark Delany
- Re: [ietf-dkim] A more fundamental SSP axiom Michael Thomas
- Re: [ietf-dkim] A more fundamental SSP axiom Hector Santos
- Re: [ietf-dkim] A more fundamental SSP axiom John Levine
- RE: [ietf-dkim] SSP requirements Bill.Oxley
- [ietf-dkim] punting into near-term standardization Dave Crocker
- Re: [ietf-dkim] A more fundamental SSP axiom Mark Delany
- RE: [ietf-dkim] A more fundamental SSP axiom Bill.Oxley
- Re: [ietf-dkim] SSP requirements Mark Delany
- RE: [ietf-dkim] SSP requirements John L
- RE: [ietf-dkim] SSP requirements Bill.Oxley
- Re: [ietf-dkim] SSP requirements John Levine
- Re: [ietf-dkim] A more fundamental SSP axiom Douglas Otis
- Re: [ietf-dkim] punting into near-term standardiz… Arvel Hathcock
- Re: [ietf-dkim] A more fundamental SSP axiom Hector Santos
- Re: [ietf-dkim] SSP requirements Michael Thomas
- Re: [ietf-dkim] SSP requirements Hector Santos
- Re: [ietf-dkim] SSP requirements John L
- Re: [ietf-dkim] A more fundamental SSP axiom Douglas Otis
- Re: [ietf-dkim] A more fundamental SSP axiom Douglas Otis
- Re: [ietf-dkim] SSP requirements Hector Santos
- Re: [ietf-dkim] SSP requirements Douglas Otis
- Re: [ietf-dkim] SSP requirements william(at)elan.net
- Re: [ietf-dkim] SSP requirements Michael Thomas
- [ietf-dkim] The problem with sender policy John L
- [ietf-dkim] DKIM Client Policy Requirement Douglas Otis
- RE: [ietf-dkim] The problem with sender policy Bill.Oxley
- RE: [ietf-dkim] The problem with sender policy John L
- Re: [ietf-dkim] SSP requirements Mark Delany
- RE: [ietf-dkim] The problem with sender policy william(at)elan.net
- Re: [ietf-dkim] SSP requirements Douglas Otis
- Re: [ietf-dkim] SSP requirements Hector Santos
- Re: [ietf-dkim] SSP requirements Dave Crocker
- Re: [ietf-dkim] punting into near-term standardiz… Hector Santos
- Re: [ietf-dkim] punting into near-term standardiz… Douglas Otis
- Re: [ietf-dkim] SSP requirements Stephen Farrell
- Re: [ietf-dkim] SSP requirements Stephen Farrell
- Re: [ietf-dkim] SSP requirements Hector Santos
- Re: [ietf-dkim] SSP requirements Hector Santos
- Re: [ietf-dkim] A more fundamental SSP axiom Scott Kitterman
- Re: [ietf-dkim] The problem with sender policy Arvel Hathcock
- Re: [ietf-dkim] SSP requirements Damon
- Re: [ietf-dkim] The problem with sender policy Damon
- Re: [ietf-dkim] SSP requirements Damon
- Re: [ietf-dkim] SSP requirements Damon
- Re: [ietf-dkim] SSP requirements Hector Santos
- Re: [ietf-dkim] The problem with sender policy Jeff Macdonald
- RE: [ietf-dkim] The problem with sender policy Bill.Oxley
- Re: [ietf-dkim] The problem with sender policy Dave Crocker
- Re: [ietf-dkim] The problem with sender policy Jeff Macdonald
- Re: [ietf-dkim] SSP requirements Douglas Otis
- Re: [ietf-dkim] SSP requirements Stephen Farrell
- Re: [ietf-dkim] A more fundamental SSP axiom Graham Murray