Re: [Endymail] spam versus cleartext

Phillip Hallam-Baker <phill@hallambaker.com> Sun, 07 September 2014 18:10 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: endymail@ietfa.amsl.com
Delivered-To: endymail@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6260A1A05D1 for <endymail@ietfa.amsl.com>; Sun, 7 Sep 2014 11:10:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.423
X-Spam-Level: *
X-Spam-Status: No, score=1.423 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, LOTS_OF_MONEY=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 fj02oE_4dNQF for <endymail@ietfa.amsl.com>; Sun, 7 Sep 2014 11:10:05 -0700 (PDT)
Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 130971A0572 for <endymail@ietf.org>; Sun, 7 Sep 2014 11:10:04 -0700 (PDT)
Received: by mail-la0-f52.google.com with SMTP id b8so5044731lan.11 for <endymail@ietf.org>; Sun, 07 Sep 2014 11:10:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=CBPIq1Pe+kOFW807+uNSsReH/qD/+bq/SgsQZ5dh/Yg=; b=RHJNOzPbxquGR8AAo9ubqIBTLeKMgq4abNNyrW7sl/PRm3QrIGYYQhk3PRD/Twa5HV 7rhsDEeubh5k69xmbnmUU5B0F2zFf6b1da+1cAoBeTIYoAAolKz8Y8ipRTBfR/Jfw9MY F7G0R/BGL4RWJ2KGsOo4UXv8H5M99qYt08d3HxBQ2lXLAknvWJ7CY6UQYrPuMH2R9tAJ D4Hfc8aZgiHCPXXVc1fXn1imku7zkgomYReW7MIn1zq2YrTltHOARSkSFtzYPHvS+7MY sH4Bl0Mg4aT45cXSiKnPeNffolIcxgrxq4BjEOImaeLWKciqzB86cB522GGRx8HUUdZJ 50tQ==
MIME-Version: 1.0
X-Received: by 10.152.1.137 with SMTP id 9mr852506lam.85.1410113402881; Sun, 07 Sep 2014 11:10:02 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.122.50 with HTTP; Sun, 7 Sep 2014 11:10:02 -0700 (PDT)
In-Reply-To: <540C7399.3060901@cisco.com>
References: <540AABF8.8000605@cisco.com> <540C5BE1.6010405@qti.qualcomm.com> <540C7399.3060901@cisco.com>
Date: Sun, 7 Sep 2014 14:10:02 -0400
X-Google-Sender-Auth: hS2rzmWCzDVEGjnoWgjnfpsV3SU
Message-ID: <CAMm+LwgsiJwjngoKcHsaP+mF=yArtx_h_YcGL98-xRb7AZ8ZAA@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Eliot Lear <lear@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/endymail/cv7g2PaOxjacKaX_mCXH3vBV47w
Cc: Pete Resnick <presnick@qti.qualcomm.com>, endymail <endymail@ietf.org>
Subject: Re: [Endymail] spam versus cleartext
X-BeenThere: endymail@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <endymail.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/endymail>, <mailto:endymail-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/endymail/>
List-Post: <mailto:endymail@ietf.org>
List-Help: <mailto:endymail-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/endymail>, <mailto:endymail-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Sep 2014 18:10:06 -0000

On Sun, Sep 7, 2014 at 11:02 AM, Eliot Lear <lear@cisco.com> wrote:
> Let's talk constraints for a moment.  Does the problem get easier if we
> say, “let's not even attempt to address transactional email”, and focus
> exclusively on h2h?  Also, is it a goal to completely do away with
> spam?  Is that a non-goal?

Transactional mail is the easiest to do and has the biggest payoff. So
no, not doing it does not help in the slightest.

I don't think we are going to be using this scheme to complete
transactions. But it has to be possible to use it for applications
such as:

* Correspondence between lawyers and clients.
* Sending statements for bank and brokerage accounts.
* Sending invoices.

We need those applications because they are applications that will
enable a lot of trade and drive a lot of commercial transactions. And
if you want to deploy an infrastructure that is going to cost $10
million+++ / yr to run you better have a story that you can deliver
benefits in the $ billions.


I don't think we need to solve the spam problem. But we can't open up
a hole that the spammers can drive a truck through.