IETF Logo Mail Archive

Re: [IETF] DMARC methods in mailman

"Patrik Fältström " <paf@frobbit.se> Mon, 26 December 2016 11:10 UTC

Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 340B31295DD for <ietf@ietfa.amsl.com>; Mon, 26 Dec 2016 03:10:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.801
X-Spam-Level:
X-Spam-Status: No, score=-5.801 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-3.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=frobbit.se
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 T96-iYA0fxcI for <ietf@ietfa.amsl.com>; Mon, 26 Dec 2016 03:10:47 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.185]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1344612951C for <ietf@ietf.org>; Mon, 26 Dec 2016 03:10:46 -0800 (PST)
Received: from [192.165.72.120] (unknown [IPv6:2a02:80:3ffc:0:4d7b:230a:e73f:c11d]) by mail.frobbit.se (Postfix) with ESMTPSA id 24F42200D8; Mon, 26 Dec 2016 12:10:43 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=frobbit.se; s=mail; t=1482750643; bh=hOr6msCrzM5nl+m/RWuN3/90lpwEZKrEUU7qo9yaM1w=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=rCuYZTla196s5T7X6bh7/VMYSXGJCfsZS6jzqGRx49FI2D4IjpykPTmYslIM/dYxo ekHaCyytHOlKnZ+gffsM3Y09QvKmZn5BnOEEDfqEeLxaXbv4LkBI9ngrHNG1XrLfSY +d5NDHSEXHi2jd2L5CWLcMpBocelGmxfdNnisWKg=
From: Patrik Fältström <paf@frobbit.se>
To: "tom p." <daedulus@btconnect.com>
Subject: Re: [IETF] DMARC methods in mailman
Date: Mon, 26 Dec 2016 12:10:42 +0100
Message-ID: <14F3D5A3-0F8C-41F1-925F-10F73308C5DD@frobbit.se>
In-Reply-To: <006201d25f63$93f56660$4001a8c0@gateway.2wire.net>
References: <001801d25d6a$4c267130$e4735390$@huitema.net> <20161223174224.9677.qmail@ary.lan> <m2y3z5alnh.wl-randy@psg.com> <F8D60ECB-C291-41D1-B313-10F641BE755D@dukhovni.org> <006201d25f63$93f56660$4001a8c0@gateway.2wire.net>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_8ABAFF6A-4501-49C4-A18F-17FBB5846B67_="; micalg="pgp-sha1"; protocol="application/pgp-signature"
X-Mailer: MailMate (2.0BETAr6072)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VchAEcJ0Fpnc9LGXnsYfMiVytU8>
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Dec 2016 11:10:48 -0000

On 26 Dec 2016, at 11:31, tom p. wrote:

> I believe that this does not invalid the origin DKIM signature, so I see
> the criterion as always modifying messages but not in a way that
> invalids DKIM signatures.

Bingo! What should have been some kind of requirement is to define the method of signing the content of portions of a message with some BCP for mailing lists.

The stress, if I may call it that, today for DKIM is that the signing is not in sync with how mailing lists are run.

   paf

v2.23.0 | Report a Bug | By Email