Re: [ietf-dkim] Fwd: SendGrid, GetResponse and Hubspot being used over DKIM "patent"

Suresh Ramasubramanian <ops.lists@gmail.com> Wed, 06 December 2017 00:29 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 BCF31128BA2 for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Tue, 5 Dec 2017 16:29:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.089
X-Spam-Level:
X-Spam-Status: No, score=-1.089 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=gmail.com
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 YEnXwOKiYeHZ for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Tue, 5 Dec 2017 16:29:50 -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 54B95128B93 for <ietf-dkim-archive@ietf.org>; Tue, 5 Dec 2017 16:29:50 -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 vB60OeQ2010862; Tue, 5 Dec 2017 16:24:42 -0800
Authentication-Results: simon.songbird.com; dkim=fail reason="verification failed; unprotected key" header.d=gmail.com header.i=@gmail.com header.b=lSuJnNDi; dkim-adsp=none (unprotected policy); dkim-atps=neutral
Received: from mail-pf0-f182.google.com (mail-pf0-f182.google.com [209.85.192.182]) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id vB60Obit010849 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT) for <ietf-dkim@mipassoc.org>; Tue, 5 Dec 2017 16:24:39 -0800
Received: by mail-pf0-f182.google.com with SMTP id e3so1440224pfi.10 for <ietf-dkim@mipassoc.org>; Tue, 05 Dec 2017 16:24:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=0O3Clu5Ljpe4msNODg5WAMeoREe88zy94ZEUeSh1Mck=; b=lSuJnNDiGmdSsYIJ5w5o8WCMy0YEKDnDFPwnGRnnOWOjlokNqrpPYbAvKWAdRqKX9p SXW2V06GB+eCASNaAflSbJgX0j3Ya6DRkGu+89aN6SzxT94kfMH2TGjKiHPyOHtBoyNa yzQhKUkFyIkttwZJiA8NQWrm+bVNCOreu0DLNxYalS6SMGpsGhpW3rQnSzFfUhRG4UcB Oa0WG6f/vrBov7rpjQgF2TG05TloQGXoZevVhGHdPR8A+ZJJTRboI3poyXlV/HY9Rcze DF2GrMNLDP50j/DJOcFY2rzTBXeRz7AviFaw2HEt8aojjVisRYfW0tRHEjmNuPzd1TlZ PMYw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=0O3Clu5Ljpe4msNODg5WAMeoREe88zy94ZEUeSh1Mck=; b=kGCoZGURjM5g1kNydKzWGNNFt8Q9XssYYQz8QKwIJIzall0Aq+AoGaigqcOt3mnvtG k5+dDeVPx+x4AnZwXSRXIZEWVOv1azbtChBt8g3nZYrixDe1Xy/5vmvODHixELFPPtsG 6ESJCUFVe4zf4R0TjT8Zn9eFC7xzHENpAKz/uKCSW+CJ6DGGbI9dzT6xRBpCsQ7y6MPM 0WSWIGyfsfeql6D6KlZsXMnbpd14Evh2s3nzHQeJgYreU0x5RJoKrEZfL7Iwble+FPMX CZcgidGXJn4x52slqBRLiVBrgfv7fwhmed/kevCp9JTzQPyNuuMH6F+5O2Z1zKfWXW56 30wQ==
X-Gm-Message-State: AJaThX7XToyvKE0Ad7xtoSYUw9ZjuZEVq+mkj3ajnr9pUARUAtw8RD2S PJWjrytxJDrx3bLHByAMiqNc7qYg
X-Google-Smtp-Source: AGs4zMaeQy8TZDnJu5hukQytkGgZrfi5lrakCp57SmfY3Bx9TBD6cSEsmbIPS0awyxVXF08uwKkSpw==
X-Received: by 10.159.216.139 with SMTP id s11mr20073703plp.441.1512519854746; Tue, 05 Dec 2017 16:24:14 -0800 (PST)
Received: from [100.80.25.19] ([106.203.119.230]) by smtp.gmail.com with ESMTPSA id c28sm1723120pfe.69.2017.12.05.16.24.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Dec 2017 16:24:13 -0800 (PST)
Mime-Version: 1.0 (1.0)
From: Suresh Ramasubramanian <ops.lists@gmail.com>
X-Mailer: iPhone Mail (15C5111a)
In-Reply-To: <20171205205038.83402.qmail@f3-external.bushwire.net>
Date: Wed, 06 Dec 2017 05:54:11 +0530
Message-Id: <3ECBBF78-C7DC-4D9F-BC98-48A031767757@gmail.com>
References: <011A51D9-76B5-4CE5-A457-3F820E2623E7@wordtothewise.com> <9F71493B-4A29-42A9-A354-2584B6A46873@wordtothewise.com> <20171205205038.83402.qmail@f3-external.bushwire.net>
To: Mark Delany <sx6un-fcsr7@qmda.emu.st>
X-MIME-Autoconverted: from quoted-printable to 8bit by simon.songbird.com id vB60Obit010849
Cc: ietf-dkim@mipassoc.org
Subject: Re: [ietf-dkim] Fwd: SendGrid, GetResponse and Hubspot being used over DKIM "patent"
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-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: ietf-dkim-bounces@mipassoc.org
Sender: ietf-dkim <ietf-dkim-bounces@mipassoc.org>

The pledge idea isn’t terribly novel either 

Anne Mitchell used a habeas haiku and then contract law to enforce that any email with that haiku in the headers had to be complaint with anti Spam best practices or would get sued.

--srs

> On 06-Dec-2017, at 2:20 AM, Mark Delany <sx6un-fcsr7@qmda.emu.st> wrote:
> 
>> On 05Dec17, Steve Atkins allegedly wrote:
>> 
>> I thought this might be of interest to DKIM implementers.
> 
>> The Asserted Patents share a common specification.
> 
> Did the claimants vacuum up the IP of the now defunct Goodmail? Reads
> somewhat similar to what they were once trying to sell. Particularly
> the "contractual" obligations of the senders.
> 
> From what I can glean, the plan is to digitally sign the email along
> the lines of S/MIME (PKI and CAs are referred to extensively and
> exclusively) and the sender include a "pledge" about the contents such
> as "no more than 5 recipients will get this email". Recipients can act
> on the pledge in the knowledge that senders apparently won't lie in
> their pledge. Or if they do lie something will happen to them -
> exactly what or how is not specified.
> 
> How the pledge is validated across the whole of Internet email is
> undefined as is what to do to the sender if the pledge is known to be
> a lie.
> 
> There are no references to DNS, no reference to how they determine
> identical mail (canonicalization), no reference to S/MIME or DKIM in
> any of their filings.
> 
> I guess the "pledge" on the part of the sender is vaguely novel but
> there is no equivalent in DKIM as far as I recall. Maybe the vendors
> you refer to have features that emulates pledges when sending email?
> 
> For moral equivalence, the Date: header is a pledge as to when the
> email was composed/sent and Content-Type: is a pledge as to how the
> MIME part has been encoded so the novelty is not even that there are
> pledges in the email, just the nature of the pledge.
> 
> To me they seem to have invented a new mail header.
> 
> 
> Mark.
> _______________________________________________
> NOTE WELL: This list operates according to
> http://mipassoc.org/dkim/ietf-list-rules.html

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