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

"Adrien de Croy" <adrien@qbik.com> Tue, 25 April 2017 09:26 UTC

Return-Path: <adrien@qbik.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 EAF65127599 for <jmap@ietfa.amsl.com>; Tue, 25 Apr 2017 02:26:26 -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, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-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 snfT2kKfw3l4 for <jmap@ietfa.amsl.com>; Tue, 25 Apr 2017 02:26:24 -0700 (PDT)
Received: from smtp.qbik.com (smtp.qbik.com [122.56.26.1]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4743C1289B5 for <jmap@ietf.org>; Tue, 25 Apr 2017 02:26:23 -0700 (PDT)
Received: From [192.168.1.146] (unverified [192.168.1.146]) by SMTP Server [192.168.1.3] (WinGate SMTP Receiver v9.0.5 (Build 5926)) with SMTP id <0001029337@smtp.qbik.com>; Tue, 25 Apr 2017 21:26:20 +1200
From: Adrien de Croy <adrien@qbik.com>
To: Paul Smith <paul@pscs.co.uk>, "jmap@ietf.org" <jmap@ietf.org>
Date: Tue, 25 Apr 2017 09:26:20 +0000
Message-Id: <em84e4d1f0-cfb3-46c6-99e0-a3398bda2bc4@bodybag>
In-Reply-To: <a9edd67d-64fc-56cc-a64d-92db10e3369d@pscs.co.uk>
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>
Reply-To: Adrien de Croy <adrien@qbik.com>
User-Agent: eM_Client/7.0.27943.0
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="------=_MB37C6EF3D-5B7C-44B8-9DC3-9326C4E5C0F0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/XlMjxT6207ZnGLCIwZMeIamGHfM>
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 09:26:27 -0000

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.

We looked several times at supporting DSN etc in our mail system, and 
balked at some of the more onerous requirements.

A lot of the extension RFCs have onerous requirements for interfacing 
with non-supporting systems.  8BITMIME springs to mind here.  So we are 
binary safe (even embedded NULLs), but don't advertise 8BITMIME due to 
not wanting to take on the responsibility of what to do when forwarding 
to another server that doesn't advertise it.  Maybe that just makes us 
lame.  Probably should revisit both these.

But we probably aren't the only ones either.

Adrien


------ Original Message ------
From: "Paul Smith" <paul@pscs.co.uk>
To: "jmap@ietf.org" <jmap@ietf.org>
Sent: 25/04/2017 8:33:24 PM
Subject: Re: [Jmap] Address Validation (was Re: Submission)

>On 24/04/2017 20:25, Ted Lemon wrote:
>>On Apr 24, 2017, at 12:14 PM, Arnt Gulbrandsen 
>><arnt@gulbrandsen.priv.no> wrote:
>>>However, the question that I understood was asked upthread is roughly 
>>>"to which recipients has x been delivered already?", and for that 
>>>particular question an unbroken implementation chain is needed from 
>>>sender to recipient.
>>
>>I think even knowing that the MTA for the admin domain of the JMAP 
>>server has successfully forwarded the message would be sufficient to 
>>be equivalent in most cases.   If someone does more, that's great, but 
>>best is the enemy of good enough.
>
>I may be wrong, but I believe you can already do that with DSN/MDNs. 
>However, I have yet to see an MUA which does it even though it doesn't 
>seem like it'd be that hard to do with the MUA requesting success DSNs 
>and parsing the responses.
>
>Maybe the JMAP server could handle the responses and somehow link the 
>status to the sent message?
>
>
>