IETF Logo Mail Archive

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

Alexey Melnikov <alexey.melnikov@isode.com> Tue, 25 April 2017 17:20 UTC

Return-Path: <alexey.melnikov@isode.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 F34F71316E9 for <jmap@ietfa.amsl.com>; Tue, 25 Apr 2017 10:20:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.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 GTUDBBcAi4SY for <jmap@ietfa.amsl.com>; Tue, 25 Apr 2017 10:20:34 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 2E6571316F0 for <jmap@ietf.org>; Tue, 25 Apr 2017 10:19:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1493140790; d=isode.com; s=june2016; i=@isode.com; bh=q9nUHDdJ17ekcdbFPfA/Wqq+X90Wt0AD3Zf2Vs1MbGo=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=mIBSzyubpi0qvK4ec7+DThoQkXX5wQZmmhZDgKT2rHr9P39dDe+Z5IC74kHm2AhUVfJYf4 q5a2x9r8nQ9WitdvAeRTCeSEniZsAbYzl7n/hTvaKHYpvCE6PUm7GNn9gifA8NcTxZwXBa JZa1AFYT7AMnICZs5RE8cPmz9ryalGw=;
Received: from [192.168.8.184] ((unknown) [82.113.183.179]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <WP-FNQB2XS3w@waldorf.isode.com>; Tue, 25 Apr 2017 18:19:49 +0100
X-SMTP-Protocol-Errors: NORDNS PIPELINING
From: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: iPad Mail (14A456)
In-Reply-To: <A29BDC33-3B42-46A0-8272-9DD6CC771A0F@fugue.com>
Date: Tue, 25 Apr 2017 18:41:04 +0100
Cc: Paul Smith <paul@pscs.co.uk>, jmap@ietf.org
Message-Id: <329861C7-3822-4587-AE04-A6C28982BEDD@isode.com>
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> <A29BDC33-3B42-46A0-8272-9DD6CC771A0F@fugue.com>
To: Ted Lemon <mellon@fugue.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="Apple-Mail-EA048C24-7364-40FD-8779-44F677A6A820"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/C1F-xL9cySjuHEaSsB-KJAwtfx4>
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 17:20:39 -0000

> On 25 Apr 2017, at 14:41, Ted Lemon <mellon@fugue.com> wrote:
> 
>> On Apr 25, 2017, at 4:33 AM, Paul Smith <paul@pscs.co.uk> wrote:
>> 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.

I've done this in a MUA that talks IMAP. While further integration in JMAP would be nice, I don't think this is either hard or that it is the first order of priorities for this group.

> One of the stated goals of the JMAP work is to remove one of the major pain points in writing MUAs: IMAP (specifically the lack of consistent implementation, which causes interop issues).   So perhaps we will see more MUA innovation.

v2.23.0 | Report a Bug | By Email