IETF Logo Mail Archive

Re: Scope for self-destructing email?

Matthew Pounsett <matt@conundrum.com> Mon, 14 August 2017 19:41 UTC

Return-Path: <matt@conundrum.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 0AB091323D4 for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 12:41:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=conundrum-com.20150623.gappssmtp.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 T8KAhJV6DB4R for <ietf@ietfa.amsl.com>; Mon, 14 Aug 2017 12:41:00 -0700 (PDT)
Received: from mail-ua0-x231.google.com (mail-ua0-x231.google.com [IPv6:2607:f8b0:400c:c08::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 144BE1323A6 for <ietf@ietf.org>; Mon, 14 Aug 2017 12:40:59 -0700 (PDT)
Received: by mail-ua0-x231.google.com with SMTP id q25so40615838uah.1 for <ietf@ietf.org>; Mon, 14 Aug 2017 12:40:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=conundrum-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=sbVAt+hoK6dYSofDAqR42C7CzZ2qg/w3Ofi2buSz37U=; b=lsYOrcuIwoigvF7lG5e/SVnWPvB1zzbUnwphR0PMYqrR15a50hk4ARp6blEljOUn2n yodPqylwXmikk/3zSK0b5Y6R0JVWb+ZePHpksueKmut+Sd8uaUPg7mXnjsRm/kS38R7o XZLnagQJT7fANn+30Cic45+ff6J9NnE+ZNeWXJ23BSl+E57E2u/XgwjuLFgeirsexlGv ENjpOxTptPCmOeGPYR3jKH0FBghID9OncWM8IMsEKs+Y26AiGnhCWyr3wXr+QUEbJ3pt VA56lghYzfNmSBTA33fU10dlB81d9sE3kSTfPjBeTfyb02SimEA3mBHXYuaxFFdOVxyF Vn9w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=sbVAt+hoK6dYSofDAqR42C7CzZ2qg/w3Ofi2buSz37U=; b=XhZAZeijcWB5+n0pcCl1ROYBONSVQMzRXpFBjCC1yQHLD5kgYOIxpVbFO3N47g1n9Z iQaYnVNmwVrVHXGTBvkME99BIIE1u2+5Pi/awAEmK3W6PPXjHYYTPLlqNgm7oFJ2Gyui Lpkijyo4YLq6+EqPDKF6zL9ztRvwRggc+YxL02FfpQEgmzX9s+8IKhyGoW0627gfNtwv /RRDY50SJ7xugI993wOkjFdAA6VFKy6UfQbMxRcoUvMh9VBbs/3tDX0G/XD72KyValCq YI5+V7c/uCTgJrflsULWBo70w1Axd/wcPFz/+UU6Hq9kTkhdtl8DXiPEZaPND9olbOmk 7slg==
X-Gm-Message-State: AHYfb5hURD/7zo4/IKCCHWvSh4tRCW+S7WKvEqOpOxJ27kvAQY1RmUT+ qxHl08VTNqDPukX+qoeisWJxzH1yWGFD
X-Received: by 10.176.81.34 with SMTP id e31mr18426934uaa.73.1502739658581; Mon, 14 Aug 2017 12:40:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.84.74 with HTTP; Mon, 14 Aug 2017 12:40:58 -0700 (PDT)
In-Reply-To: <c734e0d7-e83a-4fb3-8cc2-a24e227b50b9@email.android.com>
References: <CAKHUCzxja6D8jXz_kR6VaGZ21xNV0aw200956f9ESb-5NkhNEA@mail.gmail.com> <c734e0d7-e83a-4fb3-8cc2-a24e227b50b9@email.android.com>
From: Matthew Pounsett <matt@conundrum.com>
Date: Mon, 14 Aug 2017 15:40:58 -0400
Message-ID: <CAAiTEH9zg2Pk=KZTJ84JP3S5g+t9P8TXBsm3T=s7zOybV6SsJA@mail.gmail.com>
Subject: Re: Scope for self-destructing email?
To: Matthias Merkel <moritz30@moritz30.de>
Cc: Dave Cridland <dave@cridland.net>, vaibhav singh <vaibhavsinghacads@gmail.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c1912c68a90d30556bbd799"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2uqzLv4xNMU5cDDaw2lv5lMPhRQ>
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: Mon, 14 Aug 2017 19:41:02 -0000

On 14 August 2017 at 15:24, Matthias Merkel <moritz30@moritz30.de> wrote:

> How about adding a way to tell if a SMTP server supports self-destructing
> emails and if it doesn't tell the user it doesn't and if they want to send
> it without self destruction
>

You have the same enforceability problem.   In the first case the request
is basically, "you MUST delete this message on the date requested, but if
you don't you MUST send a notice saying you didn't do that, but if you
don't... nothing happens."   Just as nothing stops the receiving server
from never deleting the message and never telling you, there's nom way to
force the receiving server to tell you the truth about what features it
implements.

As a simple advisory feature I'd probably ignore it.  Since there's never
any way to know whether the receiving server will live up to its promise,
you can never trust that it will, and so why send the info in the first
place?

v2.23.0 | Report a Bug | By Email