Re: Scope for self-destructing email?

"John Levine" <johnl@taugh.com> Wed, 16 August 2017 22:57 UTC

Return-Path: <johnl@taugh.com>
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 1A4C01323A4 for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 15:57:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 hCVDfqN1yxey for <ietf@ietfa.amsl.com>; Wed, 16 Aug 2017 15:57:01 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3220613235C for <ietf@ietf.org>; Wed, 16 Aug 2017 15:57:00 -0700 (PDT)
Received: (qmail 34124 invoked from network); 16 Aug 2017 22:56:59 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 16 Aug 2017 22:56:59 -0000
Date: Wed, 16 Aug 2017 22:56:37 -0000
Message-ID: <20170816225637.4431.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Cc: vaibhavsinghacads@gmail.com
Subject: Re: Scope for self-destructing email?
In-Reply-To: <CACZ1GiooBdEZ_YcBZPQNFkbT0DsGf-Cu25fPYzWcLamLUAH+TA@mail.gmail.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ROsgf6KDSeDytaNjpL-L50N_Jcw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 16 Aug 2017 22:57:03 -0000

In article <CACZ1GiooBdEZ_YcBZPQNFkbT0DsGf-Cu25fPYzWcLamLUAH+TA@mail.gmail.com> you write:
>This seems to work for me. Any problems which could come up with having a
>central authority for this feature?

Many.  What if I tell the central authority that I implement
self-destructive e-mail but I'm lying?  How could the central
authority tell?  I'm pretty sure I can pass whatever audits they make
since they have no way to tell what data I'm hiding in places they
can't see.

>4.) A really boiled down version of ephemeral mails could just mark the
>mail "outdated" if the information provided in the mail is not expected to
>hold good after some time, instead of actually expunging the mail.

As others have said, that feature has come and gone many times in the past.  In
netnews, which is similar in some ways to mail, there's an Expires: header which
works reasonably well, typically used to mark messages that stop being interesting
after some point like weather forecasts or event reminders.  There's no guarantee
that anyone will follow the advice, and you certainly can't use it to force stuff
to disappear, but it's been occasionally useful.

R's,
John