IETF Logo Mail Archive

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

Bron Gondwana <brong@fastmail.fm> Mon, 24 April 2017 01:21 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 64054127735 for <jmap@ietfa.amsl.com>; Sun, 23 Apr 2017 18:21:57 -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=Hgh/LsKC; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=XAD7Iz+c
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 uRdy2-l2NvdL for <jmap@ietfa.amsl.com>; Sun, 23 Apr 2017 18:21:56 -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 65BCF124217 for <jmap@ietf.org>; Sun, 23 Apr 2017 18:21:56 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id C01FC209BE for <jmap@ietf.org>; Sun, 23 Apr 2017 21:21:55 -0400 (EDT)
Received: from web2 ([10.202.2.212]) by compute6.internal (MEProxy); Sun, 23 Apr 2017 21:21:55 -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=XAX8aWWMzKm79bHFW20AzU0AYLCHz n0qOoy5f/oX86c=; b=Hgh/LsKC4OLT7SxKJBdqbaPyAvQ35faJIi/dFilrnaqm9 YS3If/M+Sen0FHJ87q57KbtMUwhJAqsQGW04DNkdXGFjPU1hrjEG7rwB5+/6k1JK 6GPIbTaynSs9meSKmDtpnJ+8GuFuAAxv7qEEsxL5FlD01pJvZzVOkM+dpSh2p8pP kG0F8wINqFhybN97kd8yGu/Zl+3UNAiTQRKLrvE9aIFAwIdigbNqmJictD+pYH40 CFH81G5wHR16XleMOSvWumdVVdOAohrSsLa4UPonRREOr7BkmLFUrVjhJZpTyuWZ R8c/zVWcbeAHKDhl4q9qD1BNWxuim4ohUIhnGwgpg==
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=XAX8aW WMzKm79bHFW20AzU0AYLCHzn0qOoy5f/oX86c=; b=XAD7Iz+cyEPRtojTkMwuKb lVJnFVka4YEjPmaxZd5wUel6m/pYYF8xaPXEzSh7abQyJP+3aWClOO7r4uWO3pQC PhY5xO55OqfOxbEWlOWY8Tsf0c6VXGfOmtd9ojWKC4Ud/f+kP9qhsYgFqaZrzmOc xOFWTAfDwSFdiBDGN1iBLcblvXQy6ugzmH3zulPsyOcW48jluJ3D2+CsBz1l/7a3 Uj4V2zwfxQfZRMj5q6u3CiR+epggGGHN+wY+xldNpAbnJNO6xryzczXxRfshx7+Q VLHQY4REuYDMugN78Ae/Dwn/MV1d26j0Nkci4L0nEX/gjGhNhP1D/vDSx3cLZ4Ig ==
X-ME-Sender: <xms:M1P9WFydnP0crmnbUgWrrtxyOYzPYzhOP3y8G4sz96KdKWd0Nz9IYw>
Received: by mailuser.nyi.internal (Postfix, from userid 99) id 9504062737; Sun, 23 Apr 2017 21:21:55 -0400 (EDT)
Message-Id: <1492996915.3310412.953749536.0F1C8B46@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: <em2713a97d-2fd2-421e-9c51-7ad1e5ae84c9@bodybag>
References: <emd3533c0d-dc08-45c3-801c-07972858ad64@bodybag> <20170421001702.24991.qmail@ary.lan> <em7b8ab713-d303-46e1-b0de-eec9f43f18e0@bodybag> <00616B85-F365-4B1F-82EA-2FF2623CED77@oracle.com> <em2713a97d-2fd2-421e-9c51-7ad1e5ae84c9@bodybag>
Date: Mon, 24 Apr 2017 11:21:55 +1000
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/95PLYpYN-quGyUg0hR9CoOr-A6w>
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 01:21:57 -0000

On Sat, 22 Apr 2017, at 11:34, Adrien de Croy wrote:
> 
> "two mechanisms to perform the same function is poor design"
> 
> Sorry I missed this one on the Mt Sinai tablets.

There's no need to be nasty.  Chill it please.  We're a professional working group.

Chris Newman wrote:
> This is quite extensible and I believe this specific functionality is 
> in-scope of the JMAP charter as Submission (RFC 6409) is explicitly 
> in-scope. Doing address validation this way is already quite powerful. 
> For example, if the submission server chooses to implement the SMTP 
> 251/551 response codes for local users, the mail client gains the 
> ability to prompt the user to correct the address book entry for that 
> recipient.

Without getting bogged down in exact details just yet, we should address this question:

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.

Cheers,

Bron.

-- 
  Bron Gondwana
  brong@fastmail.fm

v2.23.0 | Report a Bug | By Email