IETF Logo Mail Archive

Re: [Jmap] DSN and MDN in JMAP

Ned Freed <ned.freed@mrochek.com> Wed, 19 July 2017 09:24 UTC

Return-Path: <ned.freed@mrochek.com>
X-Original-To: jmap@ietfa.amsl.com
Delivered-To: jmap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70A2C131C45 for <jmap@ietfa.amsl.com>; Wed, 19 Jul 2017 02:24:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.003
X-Spam-Level:
X-Spam-Status: No, score=-2.003 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mrochek.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 eO89MzYrS_zR for <jmap@ietfa.amsl.com>; Wed, 19 Jul 2017 02:24:49 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [68.183.62.69]) (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 3B2B1131C3F for <jmap@ietf.org>; Wed, 19 Jul 2017 02:24:49 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QGVJGULGLC007NFH@mauve.mrochek.com> for jmap@ietf.org; Wed, 19 Jul 2017 02:19:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mrochek.com; s=mauve; t=1500455985; bh=FJ4rSXDNWkJF+ojaMGLYaeItozw9/pRgbFkTMES/iRA=; h=Cc:Date:From:Subject:In-reply-to:References:To; b=e+vF30Zx+TujmAujS+Vu214+E4C3/Q4yPePnPTqVzaMH4QGgcob1TkuLZOL0kaejo rsVP3r4zE0pph2xgatW9UxE7B5axiegPaKpICE0CN48LZE/7koWrH/EEXrz063GUeE JTZ11Si24hejHQYmAsUppoyBDWVLeWHDxv2uKedE=
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: TEXT/PLAIN; CHARSET="us-ascii"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QGGZN1ZVAO0000D4@mauve.mrochek.com>; Wed, 19 Jul 2017 02:19:44 -0700 (PDT)
Cc: jmap@ietf.org
Message-id: <01QGVJGTAE800000D4@mauve.mrochek.com>
Date: Wed, 19 Jul 2017 02:14:59 -0700
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Wed, 19 Jul 2017 16:49:02 +1000" <1500446942.4021701.1045523016.632D0EF4@webmail.messagingengine.com>
References: <71E3B9BE-C58C-40DF-AA63-EB4B94334DD5@oracle.com> <1500398084.797896.1044865312.4893BFE7@webmail.messagingengine.com> <1500446942.4021701.1045523016.632D0EF4@webmail.messagingengine.com>
To: Bron Gondwana <brong@fastmailteam.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/-XWlXXq1gNqlouP-GPZstMWnGYg>
Subject: Re: [Jmap] DSN and MDN in JMAP
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: JSON Message Access Protocol <jmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jmap>, <mailto:jmap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jmap/>
List-Post: <mailto:jmap@ietf.org>
List-Help: <mailto:jmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jmap>, <mailto:jmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 09:24:50 -0000

> Regarding "delivered" there is a 4th state which you haven't captured here
> which is "definitely not yet" while the message is still in an outbound queue. 
> That's not quite the same as unknown.  Obviously a future-send email would also
> have that state.

Why are we repeating prior work here? In regards to
submission-transmission-delivery, the model for all of this was worked out as
part of the message tracking work published in RFCs 3885-3888. In this
particular case, you're talking about the action field defined in RFC 3886
section 3.3.3. The specific state you're desribing is the "delayed" state.

				Ned

v2.23.0 | Report a Bug | By Email