IETF Logo Mail Archive

RE: [ietf-dkim] The problem with sender policy

John L <johnl@iecc.com> Sun, 06 August 2006 01:21 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G9XL0-0005T5-Gy for ietf-dkim-archive@lists.ietf.org; Sat, 05 Aug 2006 21:21:54 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G9XKw-0005xm-TU for ietf-dkim-archive@lists.ietf.org; Sat, 05 Aug 2006 21:21:54 -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 k761LKKJ002052; Sat, 5 Aug 2006 18:21:21 -0700
Received: from xuxa.iecc.com (xuxa.iecc.com [208.31.42.42]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with SMTP id k761LCjQ002027 for <ietf-dkim@mipassoc.org>; Sat, 5 Aug 2006 18:21:13 -0700
Received: (qmail 21716 invoked from network); 6 Aug 2006 01:20:47 -0000
Received: from simone.iecc.com (208.31.42.47) by mail2.iecc.com with QMQP; 6 Aug 2006 01:20:47 -0000
Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 Aug 2006 01:20:47 -0000
Date: Sat, 05 Aug 2006 21:20:47 -0400
From: John L <johnl@iecc.com>
To: Bill.Oxley@cox.com
Subject: RE: [ietf-dkim] The problem with sender policy
In-Reply-To: <BB621D48443A854A89D86528F915864C0215F77B@CATL0MS02.corp.cox.com>
Message-ID: <20060805212005.D17637@simone.iecc.com>
References: <BB621D48443A854A89D86528F915864C0215F77B@CATL0MS02.corp.cox.com>
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
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.1 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f

> All DKIM does for me is to get a case of who to kvetch at when I get
> some real nasty spam and senders policy will assist me in determining
> that.

Pretty much.  If you have a whitelist, it'll also help you recognize 
people on the whitelist.

> In no way does accreditation=DKIM

Quite right.  That's why Paul and I set up DAC.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Information Superhighwayman wanna-be, http://johnlevine.com, Mayor
"I dropped the toothpaste", said Tom, crestfallenly.
_______________________________________________
NOTE WELL: This list operates according to 
http://mipassoc.org/dkim/ietf-list-rules.html

v2.23.0 | Report a Bug | By Email