Re: [ietf-dkim] draft-ietf-dkim-mailinglists-02 review

Douglas Otis <dotis@mail-abuse.org> Mon, 13 September 2010 18:25 UTC

Return-Path: <ietf-dkim-bounces@mipassoc.org>
X-Original-To: ietfarch-ietf-dkim-archive@core3.amsl.com
Delivered-To: ietfarch-ietf-dkim-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9ACB83A69F7 for <ietfarch-ietf-dkim-archive@core3.amsl.com>; Mon, 13 Sep 2010 11:25:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.285
X-Spam-Level:
X-Spam-Status: No, score=-106.285 tagged_above=-999 required=5 tests=[AWL=0.314, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JISlKh0J2E4g for <ietfarch-ietf-dkim-archive@core3.amsl.com>; Mon, 13 Sep 2010 11:25:13 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 5E3743A6A7B for <ietf-dkim-archive@ietf.org>; Mon, 13 Sep 2010 11:25:13 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [127.0.0.1]) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o8DIOajI015628; Mon, 13 Sep 2010 11:24:43 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=mipassoc.org; s=k00001; t=1284402285; bh=EPYELoiXp+t9uYndyPqvCRnNPQw=; h=Message-ID:Date: From:MIME-Version:To:References:In-Reply-To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=L00hVScF1CJFAmIu+ oXNs0wE8o9/v2TiwfZBPBALEnx+X/toGAGYLNIuMgUosycYvLbWPl4IZrnJIowIkbE9 ipb4cC7oqS/xjpzHYX8NilBwWqSe1I/mK0boSTh5n3WK1oT7rKI9p6GX08hgO3bjjs0 lRFFR7Pg2vTz/CHCUEoU=
Received: from harry.mail-abuse.org (harry.mail-abuse.org [168.61.5.27]) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o8DIOUs4015617 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-dkim@mipassoc.org>; Mon, 13 Sep 2010 11:24:35 -0700
Received: from sjc-office-nat-210.mail-abuse.org (gateway1.sjc.mail-abuse.org [168.61.5.81]) by harry.mail-abuse.org (Postfix) with ESMTP id DDC90A94738 for <ietf-dkim@mipassoc.org>; Mon, 13 Sep 2010 17:46:41 +0000 (UTC)
Message-ID: <4C8E6383.9050004@mail-abuse.org>
Date: Mon, 13 Sep 2010 10:46:43 -0700
From: Douglas Otis <dotis@mail-abuse.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100825 Thunderbird/3.1.3
MIME-Version: 1.0
To: ietf-dkim@mipassoc.org
References: <20100901091802.6173.qmail@joyce.lan> <op.vitxkai96hl8nm@clerew.man.ac.uk> <58CE74EC-512F-472A-8F63-682E1E52A14D@wordtothewise.com> <201009101731.57732.ietf-dkim@kitterman.com> <DE7D7AF9-6898-47B0-826C-89B4C20E7D54@wordtothewise.com> <op.viywqq0p6hl8nm@clerew.man.ac.uk>
In-Reply-To: <op.viywqq0p6hl8nm@clerew.man.ac.uk>
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (sbh17.songbird.com [127.0.0.1]); Mon, 13 Sep 2010 11:24:45 -0700 (PDT)
X-Greylist: Delayed for 00:37:47 by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.70]); Mon, 13 Sep 2010 11:24:35 -0700 (PDT)
Subject: Re: [ietf-dkim] draft-ietf-dkim-mailinglists-02 review
X-BeenThere: ietf-dkim@mipassoc.org
X-Mailman-Version: 2.1.9
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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-dkim-bounces@mipassoc.org
Errors-To: ietf-dkim-bounces@mipassoc.org

  On 9/13/10 3:57 AM, Charles Lindsey wrote:
>  On Fri, 10 Sep 2010 23:37:46 +0100, Steve Atkins
>  <steve@wordtothewise.com> wrote:
>
> > On Sep 10, 2010, at 2:31 PM, Scott Kitterman wrote:
> >> ..... If this negative event can be avoided by the simple
> >> mechanism of using a mailing list specific "Message" From, then
> >> that is a benefit.
> >
> > Rather than go into the general reasons why I think this is not
> > something that ADSP users really want, I'll give a concrete
> > example.
>
>  What ADSP users want is irrelevant. This is about what MLMs want
>  (which is most likely to ensure that submitted messages reach the
>  whole of their list without problems).

There is the human aspect of recognizing the purported author.  See:

http://tools.ietf.org/html/draft-ietf-eai-mailinglist-07

Where in the introduction there is this comment:
,---
...
Separate from these standardized list-specific header fields, and 
despite a history of interoperability problems from doing so, some lists 
alter or add header fields in an attempt to control where replies are 
sent.  Such lists typically add or replace the "Reply-To" field and some 
add or replace the "Sender" field.  Poorly-behaved lists may alter or 
replace other fields, including "From".
'---
It also seems that both the downgraded and international versions of the 
email-address would need to be recoded.

> > Lets say this mailing list rewrites the From: address in some
> > reasonably mechanical manner, and the From: field of this message
> > were rewritten as (making up syntax on the fly)...
> >
> > From: steve%blighty.com%ietf-dkim@mipassoc.org
> >
> > ... such that recipients (or their MUAs) know that this mail was
> > sent by steve@blighty.com via a mailing list at dkim.org.
> >
> > There's nothing to stop me from sending mail From:
> > billing%paypal.com%ietf-dkim@mipassoc.org, as the mailing list
> > isn't using ADSP.
>
>  Clearly, mailing lists that do things to the From: SHOULD (even MUST)
>  sign, and any RFC documenting my proposal would include that.
>
>  But yes, you could currently send a message to this list From: that
>  address, but that has nothing to do with whether my suggestion is
>  adopted or not. I suspect you would soon find yourself blacklisted by
>  the MLM.

Do you mean the MTA would become blacklisted or the subscriber being 
spoofed?  DKIM does not identify the author.

Defending the MLM might work after all subscribers and the MLM have 
adopted DKIM as a requirement for acceptance.  Otherwise this would 
expect the MLM to check policy on any percent hack email-address without 
there being any defined standard.  For example, VERP uses '=' as a 
replacement symbol for '@' when stacking addresses. BATV and SRS use '=' 
to isolate local-part components.  The '%' symbol is understood by some 
operating systems to indicate a hex conversion is desired.   :^(

-Doug

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