IETF Logo Mail Archive

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

Bron Gondwana <brong@fastmail.fm> Mon, 24 April 2017 02:04 UTC

Return-Path: <brong@fastmail.fm>
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 2DC47126C2F for <jmap@ietfa.amsl.com>; Sun, 23 Apr 2017 19:04:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.fm header.b=CIAtm5rY; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=QyBRr3ey
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 qr_1f2wy3DU7 for <jmap@ietfa.amsl.com>; Sun, 23 Apr 2017 19:03:59 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE83A120046 for <jmap@ietf.org>; Sun, 23 Apr 2017 19:03:58 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 56FA620B1A for <jmap@ietf.org>; Sun, 23 Apr 2017 22:03:58 -0400 (EDT)
Received: from web2 ([10.202.2.212]) by compute6.internal (MEProxy); Sun, 23 Apr 2017 22:03:58 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=+vnEtO+jKAq6D/IA085Z31KE9aOVW QDZGtb5+gOmImg=; b=CIAtm5rYwhpgysAEoDcpBn7eH1HUfqgbZ/Cp5Nx2c2a+Q 2blzarm1PvVPuhVMFPqaX7E4Fqt6xky1mai/QHM6pvOBcbv6YuOOn41nZ49YbCxg lil+h+5zcEfaDGaBolMt8QQt9/LmJlwYujaQKn8vR8/sS5S9ny11C9IkEDTQe+aO HAd0Yy3aXzjYlvhmVgmA3BvqOq8wS8SZKI+nRP5fyDKfOlIhbRTGo2NMG2yJSjOM x2mm4X0V33XUi6yEqXxq0/EnWI+v1pDT4/8GRsF/H9aVryxvDWfGouyG3Zan3vFf Y/wZCUUxx3uCEyh8OXb8IvQebw7Pjo1PPEu3LFX0Q==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=+vnEtO +jKAq6D/IA085Z31KE9aOVWQDZGtb5+gOmImg=; b=QyBRr3ey0me4Hi3cMoH09v Rd+aQXzofcUpqtMqEDiw1LGTPGmqjGGBm0Kp+o8tPQgkTK4vNzh9wi01Ygi/llgX Q6zvgnMqqNul/SoYpujz8IzYsYVfxLds5O197f/pB7F9vMV78MEIHkRShJgJXcUm uD9uqog9589P8qc5S+BTGA0CcMZLh+OdhvvTvDVUgcJlp2+uMqAXWBGOSf+NuLG1 GEhLBmFakLQCN2Knz6q6/1IlGgrgZQ4Zj+/giWRlXgY0KiIPtNFKe9ycy4PDw1Bm tZ9UYYwG0F/BmBqsH9xLCOMXMpZnn/VjdcLqyG9/k8shF9Fp49/hzBUMRPbipELQ ==
X-ME-Sender: <xms:Dl39WC7MSwVDt7PWYTnqV6N3eGQ8YvB31W05vVY_fRzh2fQ8X0Ocuw>
Received: by mailuser.nyi.internal (Postfix, from userid 99) id 2DC0F62737; Sun, 23 Apr 2017 22:03:58 -0400 (EDT)
Message-Id: <1492999438.3318688.953774952.11A8EA9B@webmail.messagingengine.com>
From: Bron Gondwana <brong@fastmail.fm>
To: jmap@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-75775c69
In-Reply-To: <20170424014957.39235.qmail@ary.lan>
Date: Mon, 24 Apr 2017 12:03:58 +1000
References: <20170424014957.39235.qmail@ary.lan>
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/KWXkUCMvU6HE142LaMCn_2mwUKI>
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: Mon, 24 Apr 2017 02:04:00 -0000


On Mon, 24 Apr 2017, at 11:49, John Levine wrote:
> In article <1492996915.3310412.953749536.0F1C8B46@webmail.messagingengine.com> you write:
> >Do we want JMAP-Mail to include a facility to check whether an address would be accepted for mail delivery by the server - presumably the result is a
> >tristate of [definite YES, Unknown, definite NO] via whatever response method is used.
> 
> I'm trying to think of a plausible use case for separate checks rather
> than at submission time, and also trying to think of a plausible way
> to do useful checks on non-local addresses.
> 
> The use cases I think of are pretty contrived, like someone just
> uploaded an address book and wants to prune out the bogus addresses.

I'm inclined to agree with you here that this is something best addressed as part of Addressbook handling (jmap-addressbook, when we get to that) allowing you to pre-fill known user addresses without typing them by hand!

Obviously the answer for non-local addresses would be "Unknown".  The interesting bit is having the information available to the client about whether an address is local, and hence they can get a clear indication of correctness before trying to send.  There's definitely value in that from a usability perspective, particularly in a large company or university or something where valid address lookup is available.

Bron.


-- 
  Bron Gondwana
  brong@fastmail.fm

v2.23.0 | Report a Bug | By Email