IETF Logo Mail Archive

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

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Mon, 24 April 2017 16:14 UTC

Return-Path: <arnt@gulbrandsen.priv.no>
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 93889131799 for <jmap@ietfa.amsl.com>; Mon, 24 Apr 2017 09:14:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gulbrandsen.priv.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 YYQQB9C8m5WA for <jmap@ietfa.amsl.com>; Mon, 24 Apr 2017 09:14:09 -0700 (PDT)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53B31127201 for <jmap@ietf.org>; Mon, 24 Apr 2017 09:14:08 -0700 (PDT)
Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 4C074FA005C; Mon, 24 Apr 2017 16:14:07 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1493050447; bh=Frq225x6kfqL3xZ14gb74Slc1BVZs5iVGC1T6lVE5a0=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=gnqZ7ksNj9R0mI+UUcSSUFVIXQWNbyk9NyTVxgtBTrBKwQOjfS2Kxq/ukfJytQNkq M32rR47ERjEIYKQqHaCj7JTOLipsmiOp262GHyQvtqTA3xaZhI4huZjNydfjrg0pxI aYvi/KhuXuud5RkHZ8d/2ed8ruhOCBDStaDRXI6E=
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1493050446-4383-4380/11/23; Mon, 24 Apr 2017 16:14:06 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: Cyrus Daboo <cyrus@daboo.name>
Cc: jmap@ietf.org
Date: Mon, 24 Apr 2017 17:14:01 +0100
User-Agent: Trojita/v0.5-9-g8961725; Qt/4.8.6; X11; Linux; Devuan GNU/Linux 1.0 (jessie)
Mime-Version: 1.0
Message-Id: <6319482c-e53f-4483-870b-844e23030f8c@gulbrandsen.priv.no>
In-Reply-To: <DB03A7F421F2B9E4A8C6AD1D@caldav.corp.apple.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>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/iaJLRXuOjBS-aOvS6YFWjNwsw6U>
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 16:14:11 -0000

Cyrus Daboo writes:
> At least one person has commented on this list that they have 
> implemented the extension.

Yes.

> Just because an extension is not 
> implemented by every SMTP server, it doesn't mean that the 
> extension is not useful and being used in some smaller market. 
> Clearly we don't need to build message tracking into JMAP from 
> the outset, but equally we should not design JMAP in a way that 
> would prevent it from easily being added as an extension for 
> those that want it.

I agree that 3885 (et al) have some utility even if only a few people 
implement them. 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.

Arnt

v2.23.0 | Report a Bug | By Email