IETF Logo Mail Archive

Re: [ietf-dkim] SSP requirements

Michael Thomas <mike@mtcc.com> Sun, 06 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 1G9WRc-0005Oq-DG for ietf-dkim-archive@lists.ietf.org; Sat, 05 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 1G9WRb-0005a1-1n for ietf-dkim-archive@lists.ietf.org; Sat, 05 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 k760JhCg028169; Sat, 5 Aug 2006 17:19:43 -0700
Received: from fasolt.mtcc.com (adsl-216-102-208-10.dsl.snfc21.pacbell.net [216.102.208.10]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k760JcTe028155 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-dkim@mipassoc.org>; Sat, 5 Aug 2006 17:19:38 -0700
DKIM-Signature: v=0.4; a=rsa-sha256; q=dns/txt; l=276; t=1154823539; x=115 5687539; c=relaxed/simple; s=dicks.drop.kirkwood; h=Content-Type:From:Subje ct:Content-Transfer-Encoding:MIME-Version; d=mtcc.com; i=mike@mtcc.com; z=F rom:=20Michael=20Thomas=20<mike@mtcc.com>|Subject:=20Re=3A=20[ietf-dkim]=20 SSP=20requirements|Sender:=20|To:=20Douglas=20Otis=20<dotis@mail-abuse.org> |Cc:=20John=20L=20<johnl@iecc.com>, =20=20ietf-dkim@mipassoc.org|Content-Tra nsfer-Encoding:=207bit|MIME-Version:=201.0|Content-Type:=20text/plain=3B=20 charset=3DISO-8859-1=3B=20format=3Dflowe d; bh=I6eUA/4Y7c9+EPeox20atz5FJtK9COXEukxatPrlESA=; b=Zhal+anR6W736ZeDD+/RXF7Lozu4YHB95EFlm3gX6y+kpROf7iDF6nsKTRiPJUukGJdeZXfN 8MAEP+rCKTOue04MV+n2A1CneoMlYcGzIhHUj1+cnESZbAnGATMvaabU;
DKIM-Signature: a=rsa-sha1; q=dns; l=276; t=1154823539; x=1155687539; c=re laxed/simple; s=dicks.drop.kirkwood; h=Content-Type:From:Subject:Content-Tr ansfer-Encoding:MIME-Version; d=mtcc.com; i=mike@mtcc.com; z=From:Michael=2 0Thomas=20<mike@mtcc.com>|Subject:Re=3A=20[ietf-dkim]=20SSP=20requirements| Sender:|To:Douglas=20Otis=20<dotis@mail-abuse.org>|Cc:John=20L=20<johnl@iec c.com>, =20=20ietf-dkim@mipassoc.org|Content-Transfer-Encoding:7bit|MIME-Ver sion:1.0|Content-Type:text/plain=3B=20charset=3DISO-8859-1=3B=20format=3Dfl owe d; X=v=3Dcisco.com=3B=20h=3DLnZFOizGNvYWpcCctxTTPb/mIno=3D; b=RYrvHLaevDAu91NpjqtEV+6H5oKHhRnc+n8so/j7FABLNEsYga6JQ66/A6RMInNWPtnE2NIx +gRhUVm39VDczErfLkt3lt+QBrg3OrdKxZ1cS9xNqCtv1WZSlBDbNP1X;
Received: from [192.168.0.102] (sj-natpool-220.cisco.com [128.107.248.220]) (authenticated bits=0) by fasolt.mtcc.com (8.13.6/8.13.1) with ESMTP id k760IvLl015955 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 Aug 2006 17:18:59 -0700
Message-ID: <44D5356A.9010100@mtcc.com>
Date: Sat, 05 Aug 2006 17:18:50 -0700
From: Michael Thomas <mike@mtcc.com>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; rv:1.7.3) Gecko/20040913 Thunderbird/0.8 Mnenhy/0.7.2.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Douglas Otis <dotis@mail-abuse.org>
Subject: Re: [ietf-dkim] SSP requirements
References: <20060805034058.861.qmail@simone.iecc.com> <44D4FB5A.5020704@mtcc.com> <20060805163953.Q47527@simone.iecc.com> <6D2FE363-D3F0-4242-BAB9-9E89EC5567BA@mail-abuse.org>
In-Reply-To: <6D2FE363-D3F0-4242-BAB9-9E89EC5567BA@mail-abuse.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Authentication-Results: fasolt.mtcc.com; header.From=mike@mtcc.com; dkim=pass ( sig from mtcc.com/dicks.drop.kirkwood verified; ); header.From=mike@mtcc.com; dkim=pass ( sig from mtcc.com/dicks.drop.kirkwood verified; );
X-XIPE-SCORES: dispose=pass; ACD=1.00; CLAM=0.00; COMPLY=0.00; URL=0.00; SA=0.00; HONEY=0.00;
X-Songbird: Clean, Clean
Cc: 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.2 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2

Douglas Otis wrote:

> An another policy that might be considered would be one for the DKIM  
> client


I'm sorry, I have no idea what a dkim client is. Can you in as few of 
words as
possible tell me what that is?

       Mike, rather burned out on these threads
_______________________________________________
NOTE WELL: This list operates according to 
http://mipassoc.org/dkim/ietf-list-rules.html

v2.23.0 | Report a Bug | By Email