IETF Logo Mail Archive

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

"Hector Santos" <hsantos@santronics.com> Fri, 04 August 2006 17:17 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G93IG-0006on-LE for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 13:17:04 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G93IF-0004wt-8i for ietf-dkim-archive@lists.ietf.org; Fri, 04 Aug 2006 13:17:04 -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 k74HG2tt020910; Fri, 4 Aug 2006 10:16:03 -0700
Received: from winserver.com (mail.santronics.com [208.247.131.9]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k74HFuS6020887 for <ietf-dkim@mipassoc.org>; Fri, 4 Aug 2006 10:15:57 -0700
Received: by winserver.com (Wildcat! SMTP Router v6.1.451.8) for ietf-dkim@mipassoc.org; Fri, 04 Aug 2006 13:17:59 -0400
Received: from hdev1 ([72.144.136.116]) by winserver.com (Wildcat! SMTP v6.1.451.8) with ESMTP id 1465662079; Fri, 04 Aug 2006 13:17:57 -0400
Message-ID: <00cd01c6b7e9$71204100$0201a8c0@hdev1>
From: Hector Santos <hsantos@santronics.com>
To: Michael Thomas <mike@mtcc.com>, dcrocker@bbiw.net
References: <20060802002353.U59653@simone.iecc.com> <44D0E259.7040400@mtcc.com> <20060802165510.X1168@simone.iecc.com> <44D160BD.7080209@mtcc.com> <20060802223619.E86316@simone.iecc.com> <44D24A20.6050109@mtcc.com> <20060803153457.X33570@simone.iecc.com> <44D36203.2060803@mtcc.com> <20060804112731.I21459@simone.iecc.com> <44D36B4A.2050903@mtcc.com><20060804114527.Y27352@simone.iecc.com><44D37206.7070209@dcrocker.net> <44D37621.2020905@mtcc.com>
Subject: Re: [ietf-dkim] A more fundamental SSP axiom
Date: Fri, 04 Aug 2006 13:14:20 -0400
Organization: Santronics Software, Inc.
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
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.1 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f

----- Original Message ----- 
From: "Michael Thomas" <mike@mtcc.com>

> What I have yet to hear is any sort of consituency for a monolithic
> "i sign everything" beyond the statements@bigbank scenario. 

This is probably similar to what some bloke said years ago:

   "What I have yet to hear is any sort of consituency for
    checking the validity of HELO domain or the RETURN PATH.  
    After all, what possible problems can it bring?"

or as it is officially stated in RFC 2821:

   This specification does not further address the authentication issues
   associated with SMTP other than to advocate that useful functionality
   not be disabled in the hope of providing some small margin of
   protection against an ignorant user who is trying to fake mail.

That ignorant user is now $13B world wide problem!!

Why so resistance on having an exclusive policy?  

-- 
Hector Santos, Santronics Software, Inc.
http://www.santronics.com







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

v2.23.0 | Report a Bug | By Email