IETF Logo Mail Archive

Re: [ietf-dkim] versions of RFC822 mail messages, Where is the formal definition of DKIM-Signature?

Dave Crocker <dcrocker@bbiw.net> Mon, 12 February 2018 02:22 UTC

Return-Path: <ietf-dkim-bounces@mipassoc.org>
X-Original-To: ietfarch-ietf-dkim-archive@ietfa.amsl.com
Delivered-To: ietfarch-ietf-dkim-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B2F612025C for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Sun, 11 Feb 2018 18:22:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bbiw.net header.b=rbK12dMH; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=bbiw.net header.b=hMm+xhiR
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 TZKqs3P3rpk6 for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Sun, 11 Feb 2018 18:22:26 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 307291200E5 for <ietf-dkim-archive@ietf.org>; Sun, 11 Feb 2018 18:22:26 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [127.0.0.1]) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id w1C2Ln1u032389; Sun, 11 Feb 2018 18:21:50 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bbiw.net; s=default; t=1518402114; bh=/KTgM7Fr/08WjfkIFH8O3Oe3JDTgM8xiW3Um6E6Edxc=; h=To:References:From:Date:In-Reply-To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=rbK12dMHqXF2IVCVa8UjVW7NgaszOZRi8WCw1lOVAePlaurjNlrEM7QvPY51yLRV+ OOFlH7n5CoCCa373Q5Uz2SA8NUwESslUS0fFqN6fDlpKj+5QQPzj97JUsgGicBzDag a6jBNHKp0HcR687bCqL3cEbC8F56Vb9cMdDccx4M=
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id w1C2LmBj032383 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 11 Feb 2018 18:21:48 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bbiw.net; s=default; t=1518402108; bh=mlANmqF5jbbLRKFs5V3jR3Lf/cpm/iIgwTqBIAgw+OE=; h=Subject:To:References:From:Date:In-Reply-To:From; b=hMm+xhiRtxM64YMjGxE3TlYR7DTkMW3B3Okkp5rsgfB5K83cjSUC710ZfTnNfd9VN BxfavpXarMUZFeTeqpA+KauGtX4fHST3P6VwnkA8k64uvsFor171/06K4GnBUWTCXu VwUF1d3sH4E0VH8rkacmWk2GPyHiPGM6gLrLVzWU=
To: Michael Thomas <mike@mtcc.com>, ietf-dkim@mipassoc.org
References: <20180210155011.3735B1A7DD64@ary.qy> <47dd136e-e122-9bd2-8cf1-7a712770d930@bbiw.net> <alpine.OSX.2.21.1802101244340.58081@ary.qy> <151740cf-796e-16eb-2ef5-ca296b5d4af0@bbiw.net> <84d515c0-7c76-232d-464f-3215db00d14d@mtcc.com> <e561d00e-d313-e700-77ff-6ead65a37bc9@bbiw.net> <3912f0ba-0b17-24f5-75ec-38f7465a45b6@mtcc.com> <ff024002-0f7b-8987-fad2-408adb31d8e4@bbiw.net> <e7612811-e876-ea21-f072-46d200e89159@mtcc.com>
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
Message-ID: <79c2d80c-5c35-33a2-6f50-338a0cbba58b@bbiw.net>
Date: Sun, 11 Feb 2018 18:20:42 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <e7612811-e876-ea21-f072-46d200e89159@mtcc.com>
Content-Language: en-US
Subject: Re: [ietf-dkim] versions of RFC822 mail messages, Where is the formal definition of DKIM-Signature?
X-BeenThere: ietf-dkim@mipassoc.org
X-Mailman-Version: 2.1.16
Precedence: list
List-Id: IETF DKIM Discussion List <ietf-dkim.mipassoc.org>
List-Unsubscribe: <http://mipassoc.org/mailman/options/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-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: ietf-dkim-bounces@mipassoc.org
Sender: ietf-dkim <ietf-dkim-bounces@mipassoc.org>

On 2/11/2018 5:54 PM, Michael Thomas wrote:
> You clearly have no idea what you are talking about.
> 
> Mike
> 
> _______________________________________________
> NOTE WELL: This list operates according to
> http://mipassoc.org/dkim/ietf-list-rules.html



Mike,

Please review the participation rules applicable to this list.  They are 
the same as you had so much trouble with, previously.

Then please consider unsubscribing, since restraint within the bounds of 
professional behavior appears to (continue to) be absent from your 
repertoire.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html

v2.23.0 | Report a Bug | By Email