[ietf-822] Aptness of DKIM for MLs

Alessandro Vesely <vesely@tana.it> Wed, 07 May 2014 10:06 UTC

Return-Path: <vesely@tana.it>
X-Original-To: ietf-822@ietfa.amsl.com
Delivered-To: ietf-822@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 972D11A06B2 for <ietf-822@ietfa.amsl.com>; Wed, 7 May 2014 03:06:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.773
X-Spam-Level:
X-Spam-Status: No, score=-0.773 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, MANGLED_TOOL=2.3, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ejSxvG1Q5djT for <ietf-822@ietfa.amsl.com>; Wed, 7 May 2014 03:06:48 -0700 (PDT)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 41E841A06B7 for <ietf-822@ietf.org>; Wed, 7 May 2014 03:06:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1399457202; bh=0wf4vmUrKtrFomI6Q2DByJvsX6C2ndbKiJRRsD99JiY=; l=1720; h=Date:From:To:References:In-Reply-To; b=Ad8vF8vppVIXwnmNPeSjnzW3yQCuuXxHeZL2UP65x2oMN263Va2DJvreorsw54tS1 1NwTrugqlitX2vd7YJpwH8a4AYODkL3BRGkDIQzcLiJMUShKvm++k1Es0+4DWvxp5z ECumGDzLrVRfqE/bQUVLayHZrt+xw0rVD1bKF1Bg=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.88] (pcale.tana [172.25.197.88]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k) by wmail.tana.it with ESMTPA; Wed, 07 May 2014 12:06:42 +0200 id 00000000005DC044.00000000536A05B2.00004698
Message-ID: <536A05B2.9060805@tana.it>
Date: Wed, 07 May 2014 12:06:42 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.4.0
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>, ietf-822@ietf.org
References: <20140506171238.28535.qmail@joyce.lan>
In-Reply-To: <20140506171238.28535.qmail@joyce.lan>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-822/HofFnyjUR2xzBFkY3BQTd25oqm4
Subject: [ietf-822] Aptness of DKIM for MLs
X-BeenThere: ietf-822@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of issues related to Internet Message Format \[RFC 822, RFC 2822, RFC 5322\]" <ietf-822.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-822/>
List-Post: <mailto:ietf-822@ietf.org>
List-Help: <mailto:ietf-822-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 May 2014 10:06:49 -0000

On Tue 06/May/2014 19:12:38 +0200 John Levine wrote:
> 
> Anything that says "I'm a mailing list" is only useful with some
> sort of external validation that it really is a list.

Please note that "really is a list" actually means "/good/ list".  An
unmoderated, unfiltered list, with no posting restrictions and
dubious subscription practices would technically still be a list, but
nobody would whitelist it --nor subscribe to it.

> If you have to do that anyway, you might as well use the list's
> DKIM signature as the key which doesn't involve inventing any new 
> mechanism.

A useful mechanism tells domain admins which users post to which
lists.  Domain admins can consider those posts as endorsements from
their users.

> I think it's also pretty clear that any scheme that depends on the
> DKIM signatures of incoming messages transiting mailing list software
> won't work, either.

As that is being told by the author of "A DKIM Profile to Enable
Message Forwarding", I guess I should believe it.  However, it is not
clear why.  Paul asked for Message-ID: to be signed too.[1]  I
suggested that each ML defines an h= header field list that authors'
domains can reliably sign.[2]

You mentioned even From: cannot be reliably signed because MLMs need
to "standardize" its syntax.[3]  It seems to me that eliminating some
of such gratuitous changes is the solution to DMARC-for-MLs which
minimizes the alterations in MLM software.  Are you sure it won't
work?

Ale

[1] http://www.ietf.org/mail-archive/web/ietf-822/current/msg06856.html
[2] http://www.ietf.org/mail-archive/web/ietf-822/current/msg06715.html
[3] http://www.ietf.org/mail-archive/web/ietf-822/current/msg06821.html