Re: [Jmap] Address Validation (was Re: Submission)

Cyrus Daboo <cyrus@daboo.name> Tue, 25 April 2017 13:53 UTC

Return-Path: <cyrus@daboo.name>
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 004CA12F3D6 for <jmap@ietfa.amsl.com>; Tue, 25 Apr 2017 06:53:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 bVpQaphlQrrA for <jmap@ietfa.amsl.com>; Tue, 25 Apr 2017 06:53:37 -0700 (PDT)
Received: from daboo.name (daboo.name [173.13.55.49]) (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 73528129BEC for <jmap@ietf.org>; Tue, 25 Apr 2017 06:53:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id BA17B6AEF7D6; Tue, 25 Apr 2017 09:53:36 -0400 (EDT)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i-nOln0QSSvp; Tue, 25 Apr 2017 09:53:36 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.44.178.52]) by daboo.name (Postfix) with ESMTPSA id 58A106AEF7CB; Tue, 25 Apr 2017 09:53:35 -0400 (EDT)
Date: Tue, 25 Apr 2017 09:53:33 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Adrien de Croy <adrien@qbik.com>, Paul Smith <paul@pscs.co.uk>, jmap@ietf.org
Message-ID: <CA68A753DA49B845CDCDD17A@caldav.corp.apple.com>
In-Reply-To: <em84e4d1f0-cfb3-46c6-99e0-a3398bda2bc4@bodybag>
References: <1492996915.3310412.953749536.0F1C8B46@webmail.messagingengine.com> <20170424014957.39235.qmail@ary.lan> <emb951e04d-3dc9-4244-915b-21bd272245ff@bodybag> <alpine.OSX.2.20.1704240925190.68584@ary.qy> <e41c88ed-2ed5-47b8-923c-bfac12334808@gulbrandsen.priv.no> <DB03A7F421F2B9E4A8C6AD1D@caldav.corp.apple.com> <6319482c-e53f-4483-870b-844e23030f8c@gulbrandsen.priv.no> <A9622742-D931-4975-9572-04878949EDDE@fugue.com> <a9edd67d-64fc-56cc-a64d-92db10e3369d@pscs.co.uk> <em84e4d1f0-cfb3-46c6-99e0-a3398bda2bc4@bodybag>
X-Mailer: Mulberry/4.1.0b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size="1197"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/geVd0tuDHvNPf8C3iTn8zK8RChk>
Subject: Re: [Jmap] Address Validation (was Re: Submission)
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: Tue, 25 Apr 2017 13:53:41 -0000

Hi Adrien,

--On April 25, 2017 at 9:26:20 AM +0000 Adrien de Croy <adrien@qbik.com> 
wrote:

> I think the problem with lack of support for MDN / DSN in clients may be
> due to lack of implementation in the network of support for it.
>
> If there's still a significant number of deployed systems that don't
> support it, then clients have increased doubts about its worth.  Chicken
> and egg issue again.
>
> I wouldn't presume that the reason that it doesn't appear so much in the
> wild in clients is due to lack of interest.  Maybe some MUA authors could
> be approached for comment.

Yup, I implemented DSN and MDM in Mulberry - but as you say, due to the 
fact that there is no guarantee that status will be returned, it is not 
very useful in the general case. I can't remember the last time I used DSN 
- but I'll try it out on this message just to see what happens!

However, there some environments where it may be useful - e.g. an 
enterprise which has a required policy to enforce MDM read receipt or DSN 
success (something that could be controlled via device management 
restrictions). I doubt it is something that would ever be useful for a 
non-enterprise system.

-- 
Cyrus Daboo